FAQ Library
The Feedback button routes here with the right product and section selected whenever possible. You can also search Technical Support and How-To Guides for common workflows.
178 results - All FAQ articles
Platform billing lives in the Mosari account hub when available. 1. Sign in at Mosari Login. 2. Open Platform Billing. 3. Review plans, invoices, or portal actions shown for your memberships. 4. For vendor subscriptions and marketplace purchases, also check Vendor Billing. 5. Submit Feedback from Ask Mo if a charge or invoice looks wrong—include the product and approximate date.
Mosari aims for one account relationship with product memberships. ScreenOps and other products may show plan or portal actions in Platform Billing. Vendor plans, add-ons, and marketplace credits are managed in Vendor Billing. Wedding or event payments stay inside the workspace where the payment was made.
Billing actions can be gated until plan runtime, portal access, or provider setup is ready. 1. Sign in and open Platform Billing. 2. Read any readiness or gate message on the page. 3. For vendor plans, also check Vendor Billing. 4. Do not retry card entry if the page says checkout is not live. 5. Email support@mymosari.com with the product, plan, and timestamp if access should already be active.
Platform billing covers Mosari account and product memberships managed from Platform Billing. Vendor billing covers VendorOS plans, add-ons, and marketplace purchases from Vendor Billing. Some accounts see both surfaces when they hold platform and vendor memberships.
Use the portal action on the billing page when it is enabled. 1. Sign in and open Platform Billing or Vendor Billing. 2. Choose the customer portal / manage subscription action if shown. 3. Update payment method or review invoices in the portal. 4. If the portal button is disabled, billing runtime may not be live yet. 5. Email support@mymosari.com with the product and plan if you need a manual invoice review.
Use the Feedback button on billing or pricing pages and select Billing or the affected plan, payment, subscription, or credit feature.
Vendor pricing lives on Pricing and in Vendor Billing. These areas show plan features, recurring costs, one-time costs, add-ons, and credit or token usage examples where relevant.
For vendor subscriptions, open Vendor Billing. For wedding or event payments, open the billing or payment area inside the workspace where the payment was made.
Vendor Billing can record provider-neutral purchase intents for plans, marketplace products, add-ons, and billing portal requests. Live checkout remains disabled until Stripe secrets, webhooks, price IDs, Connect readiness, compliance review, and production smoke tests are approved.
Use Vendor Billing to record the request without charging a card. 1. Open Vendor Billing. 2. Choose the plan, add-on, marketplace credit, or featured placement action. 3. Confirm the UI says it is recording a purchase intent, not charging payment. 4. Save the intent and review the returned message. 5. Wait for billing runtime activation before expecting live checkout, saved payment methods, receipts, or portal management.
The runtime status `stripe_disabled` means Mosari recorded the vendor request internally, but no live Stripe Checkout, Billing Portal, payment method, subscription, charge, or webhook fulfillment occurred. This is expected until billing runtime is approved. Submit Feedback only if the UI claimed a card was charged or the purchase should already be active.
Include these details: 1. Workspace or account name. 2. Payment type, such as subscription, vendor payment, invoice, registry, or cash fund. 3. Amount and approximate time. 4. Receipt or invoice number if available. 5. Whether the issue happened before checkout, during checkout, or after payment.
Installing Mosari as a PWA is available to all tiers. Browser push notifications are planned as a VendorOS Pro and higher feature at launch. Free and Launch vendors can keep using in-app notifications from the notification bell.
Feature gates show which tools are available for the current plan or readiness state. A page may preview a workflow while create, publish, payment, API, marketplace, or automation actions remain gated until the correct tier, entitlement, verification, or third-party runtime is active.
No. Currency and regional preferences control display formatting and launch-ready context. Tax automation, VAT/GST rules, payment provider settlement, and country-specific payment processing stay provider-gated until Mosari verifies the required rules, credentials, disclosures, and runtime behavior for that market.
A feature may be visible as a preview while gated actions are locked. 1. Read the gate banner on the page. 2. Open Vendor Billing to compare plan access. 3. Check whether the feature also needs verification, RBWA entitlement, payment runtime, API secrets, or admin approval. 4. Submit Feedback only if the banner says you should have access but the action is still disabled.
Start from Events signup or your Mosari Platform account. 1. Open Events or Create Mosari Account. 2. Create or sign in with your Mosari email. 3. Continue into the Events dashboard. 4. Create or join an event workspace. 5. Invite teammates when your role allows it.
Start with the brief and attendees, then add vendors, timeline, files, and guest-facing links. 1. Confirm event name, dates, and location in the brief. 2. Import or add attendees. 3. Add vendors and shared collaborators as needed. 4. Build timeline and file folders for production. 5. Publish registration or event page links when ready.
Mosari Events is for private, corporate, nonprofit, and hosted programs that need event workspaces without wedding-specific planning assumptions.
Open Mosari Events for private, corporate, nonprofit, and hosted events that need planning tools without wedding-specific assumptions.
Event users can manage event details, guests, vendors, timelines, communications, payments, and workspace settings based on the tools enabled for their event.
The Event Brief is the trusted source for event type, date, location, headcount, host context, goals, priorities, notes, and status. Keep it current before inviting vendors, building the public event page, or exporting packet details.
Yes. Events can use RSVP and guest management workflows for attendee tracking, responses, and event-specific planning needs.
Open the event workspace and choose Attendees. 1. Use the import or paste parser for CSV, spreadsheet, document, or copied-row data. 2. Keep one attendee per row when possible. 3. Include RSVP status, attendee type, group, meal, VIP, and accessibility columns when available. 4. Review skipped or updated rows before using the list for seating. 5. Confirm totals match the event headcount before moving into layout, seating, or packet prep.
Vendor payment flows are intended to keep payments, receipts, and status tracking inside Mosari when the vendor has the required payment setup.
Open the event workspace and choose Budget. 1. Set the total event spend ceiling. 2. Add cost items for venue, catering, AV, rentals, staffing, entertainment, signage, security, transportation, and other production needs. 3. Connect each item to a vendor or partner when possible. 4. Track estimated, committed, paid, approval status, payment status, due date, and packet notes. 5. Review pending approvals before sharing the final event packet.
Event workspaces should prioritize event-safe marketplace suggestions such as venues, catering and bar, AV, rentals, decor, staffing, entertainment, signage, security, transportation, production, livestream, and registration support. Wedding-only categories such as officiant or jeweler should not appear as event defaults.
Open the event workspace and choose Website. 1. Select a standard event template. 2. Add event title, venue, public details, logistics, and invite copy. 3. Enable RSVP when attendee responses should feed the workspace. 4. Add a donation or external payment CTA only when the event needs it. 5. Publish only after privacy, RSVP, venue, and contact details are reviewed.
Registration & Links collects event CTAs that should be visible or packet-ready: ticketing, donation, sponsor, livestream, lodging, parking, agenda, survey, external registration, and public resource links. Keep public guest links separate from private planning links.
Open the event workspace and choose Layout. 1. Add venue areas such as ballroom, foyer, stage, registration, expo, or outdoor zones. 2. Add objects for stages, tables, booths, registration desks, check-in, AV, signage, staff, security, and production zones. 3. Resize and rotate objects to match the room. 4. Mark seating-capable objects when they should feed Seating. 5. Save the layout before opening Seating or the packet builder.
Check the Layout connection first. 1. Open Layout and confirm the object still exists. 2. Confirm the object is marked as seating-capable and has capacity. 3. Save the layout after moving, resizing, rotating, renaming, or deleting objects. 4. Refresh Seating and confirm the same labels, shapes, capacities, and placement status appear. 5. Submit Feedback with the event name and object label if Seating still shows stale or missing objects.
Open the event workspace and choose Timeline. 1. Add milestones, load-in, doors, program blocks, sponsor activations, internal handoffs, show flow, and strike. 2. Assign owner, visibility, readiness, and packet notes for each item. 3. Keep public schedule details separate from internal production timing. 4. Review late or unassigned items before packet export.
Check the file record before exporting. 1. Confirm the file is attached to the correct event workspace. 2. Confirm approval status and packet-ready status are set correctly. 3. Confirm vendor visibility if the packet is vendor-specific. 4. Refresh Files and regenerate the packet. 5. Submit Feedback with the file name, event name, and packet section if the source record is saved but absent.
Try these steps: 1. Sign out of the current workspace. 2. Return to the correct product login: Wedding Login, Events Login, or Vendor Login. 3. Sign in again. 4. If you still land in the wrong workspace, submit Feedback from the login page so Mosari can review account-type routing.
Open Mosari Events. 1. Create or open an event workspace. 2. Enter event details such as date, location, host, and event type. 3. Add guests or attendees. 4. Invite vendors or collaborators when needed. 5. Track planning items from the event dashboard.
Use the event workspace as the source of truth. 1. Confirm event date, location, host, and attendee details. 2. Review vendor records and payment status. 3. Confirm timeline, task, and file attachments. 4. Add production notes, approvals, and custom fields needed by staff. 5. Export or share the packet when the event export workflow is enabled.
Check whether the vendor is attached to the event workspace. 1. Open the event workspace. 2. Confirm the vendor record is linked to the event. 3. Confirm any contract, task, file, or payment record is attached to that vendor. 4. Regenerate the packet. 5. Submit Feedback with the event name and vendor name if linked records are still absent.
Each browser controls its own install prompt. Chrome and Edge may show a native Install app prompt. iOS Safari uses Share then Add to Home Screen. Mosari shows the best available option for the current browser while keeping the same dashboard URLs.
Mosari Platform is one account for every Mosari product. Create a Mosari account once, then activate ScreenOps, WeddingOS, EventOS, VendorOS, and Storefronts as memberships—not separate identities. Start at Mosari Platform or Create Mosari Account.
ScreenOps is live today for window and door companies. WeddingOS, EventOS, VendorOS, and Storefronts share the same Mosari account model as they ship. Use Mosari Platform to choose your business type, or open Activate ScreenOps when you are ready to start.
Create one Mosari Platform account, then activate the product you need. 1. Open Create Mosari Account. 2. Enter your email, name, and password. 3. Verify your email if prompted. 4. Choose the product to activate, such as ScreenOps, Wedding, Events, or VendorOS. 5. Continue into that product dashboard with the same login.
Use the login for the product you need—the same Mosari account works across products. 1. Platform / ScreenOps: Sign in to Mosari. 2. Wedding: Wedding Login. 3. Events: Events Login. 4. VendorOS: Vendor Login. 5. If you land in the wrong workspace, sign out and use the correct product login link.
Use account recovery from the login screen. 1. Open the login page for your product, such as Mosari Login or Wedding Login. 2. Choose Forgot password. 3. Enter the email on your Mosari account. 4. Open the reset link from your email. 5. Set a new password and sign in again. If you do not receive email, check spam, confirm the email spelling, and submit Feedback with the account email so Mosari can help.
ScreenOps is Mosari’s operations product for window and door companies. It helps teams manage inquiries, consultations, production, field work, invoicing, and customer communication in one workspace. Activate it from Mosari Platform after you create or sign in to your Mosari account.
WeddingOS is Mosari’s wedding planning product for couples and helpers. Plan guests, RSVPs, websites, layout, seating, budget, vendors, and shared workspaces from one account. Start at Wedding Sign Up or Create Mosari Account.
EventOS helps event companies coordinate attendees, vendors, timelines, files, seating, and day-of workflows. Open Events or activate EventOS from your Mosari Platform account when available.
VendorOS is Mosari’s operations product for wedding and event vendors. Manage leads, customers, quotes, invoices, jobs, storefronts, marketplace, and billing from Vendor Dashboard.
Storefronts are public web pages and marketplace profiles that capture inquiries and showcase packages, services, and galleries. Vendors manage them from VendorOS, and visitors can browse marketplace or vendor-site pages on Mosari.
Activate ScreenOps as a membership on your Mosari account. 1. Create or sign in at Mosari Platform. 2. Choose Activate ScreenOps / create platform account when prompted. 3. Complete any business profile steps shown. 4. Continue into the ScreenOps workspace from the activation success screen or product link. 5. If activation is missing, email support@mymosari.com with your account email.
Use the product login or homepage for the workspace you need. The same Mosari identity can hold multiple memberships. 1. Sign in once with your Mosari email. 2. Open Wedding, Events, Vendor, Platform, or ScreenOps from its product URL. 3. If you land in the wrong product, sign out and use that product’s login link. 4. Ask Mo or email support@mymosari.com if a membership you expect is missing.
Use this fix path: 1. Confirm you signed in with the invited or registered email. 2. Open the correct product login: Platform, Wedding, Events, or Vendor. 3. Sign out of other Mosari sessions if you use multiple accounts. 4. Retry the product homepage. 5. Email support@mymosari.com with the account email, product, and what you expected to see.
Try these steps: 1. Confirm the email spelling on the forgot-password form. 2. Check spam and promotions folders. 3. Wait a few minutes and request a new reset link. 4. Confirm you are using the same email as your Mosari account. 5. Email support@mymosari.com if no reset message arrives after another request.
Use Ask Mo on the platform homepage for guided answers, or browse published FAQs. 1. Ask Mo from Mosari Platform. 2. Open FAQ and filter by product or section. 3. Review product resources and help links on each product subdomain. 4. For ScreenOps docs, use the ScreenOps documentation link when shown in product marketing. 5. Email support@mymosari.com if a workflow is not documented yet.
Choose the product that matches your role. 1. Couples and wedding helpers: WeddingOS at wedding.mymosari.com. 2. Event companies and hosts: EventOS at event.mymosari.com. 3. Wedding or event vendors: VendorOS at vendor.mymosari.com. 4. Window and door companies: ScreenOps from mymosari.com. 5. Account, memberships, and platform billing: Mosari Platform. If you are unsure, create one Mosari account first, then activate the product you need.
Your Mosari Platform account is the hub for identity and memberships. 1. View activated products and launch them. 2. Manage organizations and memberships. 3. Open platform billing when available. 4. Update security settings such as email verification and MFA. 5. Access developer settings when enabled for your account. Start at Platform dashboard.
Verify email from Platform security settings. 1. Sign in at Mosari Login. 2. Open Platform Security. 3. Send or confirm the email verification request. 4. Open the message in your inbox and complete verification. 5. Return to Platform if the page still shows unverified.
Use Platform security settings when MFA is available for your account. 1. Sign in and open Platform Security. 2. Find the MFA / authenticator section. 3. Follow the setup steps shown for your authenticator app. 4. Save backup codes if Mosari provides them. 5. Sign out and sign back in once to confirm MFA works.
Launch ScreenOps from your Mosari account or the ScreenOps entry link shown after activation. 1. Sign in at mymosari.com. 2. Open Platform and look for ScreenOps under products. 3. Choose Launch / Open ScreenOps when membership is active. 4. If ScreenOps is not listed, complete activation first. 5. Email support@mymosari.com with your account email if activation shows active but launch is missing.
Use this fix path: 1. Confirm you are signed in with the Mosari email used for activation. 2. Retry activation from Mosari Platform. 3. Open Platform and check ScreenOps membership status. 4. Clear a stuck session by signing out and signing in again. 5. Email support@mymosari.com with the account email and what you see on the activation or dashboard screen.
No. One Mosari account can hold multiple product memberships. Use the product homepage or login link for the workspace you need, but keep the same email and password. If a product asks you to create an account, sign in with your existing Mosari identity when possible.
Use the Help surfaces on Mosari Platform. 1. From the public homepage, open Help or gateway help. 2. When signed in, open Help from the Platform account nav or platform help. 3. Browse FAQs, how-tos, and technical support grouped for account and product topics. 4. Use Ask Mo for a guided answer from any Mosari page where Mo is available. 5. Email support@mymosari.com if you still need a person.
Try these steps: 1. Confirm Caps Lock is off and the email spelling matches your Mosari account. 2. Use Forgot password from Mosari Login or your product login page. 3. Complete the reset from the email link. 4. Sign in again with the new password on the same product login you expected. 5. Email support@mymosari.com if reset succeeds but sign-in still fails.
Event shared workspaces should show role-specific views. Hosts need full planning context, vendors need their tasks/files/setup notes, customers or sponsors need their approved details, staff need operational assignments, and read-only collaborators need packet-safe information without edit access.
Shared Workspaces connect couples, event users, vendors, and approved collaborators around a specific planning relationship. They are designed to keep conversations, tasks, files, invoices, proposals, and approvals attached to the right customer or event instead of scattered across separate tools.
Start from the workspace where the collaboration belongs. 1. In Weddings, open Wedding Vendors or the related planning section. 2. Choose the vendor, collaborator, or invite action when available. 3. Enter the contact details and choose the role or access level. 4. Send the invite. 5. Ask the recipient to sign in through the correct product login if they cannot open the invite.
Shared workspace items should stay attached to the relationship that created them. 1. Create tasks from the relevant customer, vendor, quote, invoice, or planning area. 2. Upload files from the workspace instead of sending them separately. 3. Keep invoices and proposals tied to the vendor or customer record. 4. Review activity history before approving changes. 5. Use direct workspace links when you need someone to review a specific item.
Try these steps: 1. Confirm the invite was sent to the same email they use to sign in. 2. Confirm they are using the correct login, such as Wedding Login, Events Login, or Vendor Login. 3. Check whether the invite expired or was revoked. 4. Confirm their role allows access to that page or tool. 5. Submit Feedback with the workspace name, invited email, and page path if access still fails.
Use this fix path: 1. Ask the workspace owner or vendor admin to resend the invite. 2. Use the newest invite link only. 3. Sign out of other Mosari accounts before opening the link if you use multiple accounts. 4. Sign in with the invited email address. 5. If the link still fails, submit Feedback from the login page and include the invited email and product you are trying to access.
A customer portal claim link connects a customer or couple account to a vendor relationship. The link opens Customer Portal Claim, asks the recipient to sign in or create an account, and then records the claim against the vendor customer record.
Open the claim link your vendor sent. 1. Confirm the URL includes a token parameter. 2. Create an account or sign in with the email the vendor invited. 3. Choose Claim portal access. 4. Wait for the success message. 5. Continue to the workspace, customer record, or dashboard shown after the claim completes.
Try these steps: 1. Confirm you are using the newest link from the vendor. 2. Check that the link includes token= in the URL. 3. Sign out of other Mosari accounts before opening the link. 4. Sign in with the invited email address. 5. If the page says the invite is missing, expired, or already claimed, ask the vendor to send a fresh portal invite.
Workspace roles control which people can see or change shared records. A member may be able to view files, invoices, tasks, comments, or approvals without having permission to edit settings, invite other users, or change billing-related records.
Check access in this order: 1. Confirm the member accepted the invite with the correct email. 2. Confirm their role allows the tool. 3. Confirm the workspace family is correct, such as wedding, event, or vendor client. 4. Confirm the record is attached to that workspace. 5. Submit Feedback with the workspace name, member email, missing tool, and page path if the role looks correct.
Mosari uses your account regional preferences to format money, dates, times, and language-ready copy across dashboards, shared workspaces, packets, storefront inquiries, messages, and Ask Mo. New accounts start with launch-safe defaults from browser or request context when available, and users can update country or region, currency, timezone, and language or date format from account settings.
Open Settings for your account type. 1. Go to Wedding Settings, Events Settings, or VendorOS Settings. 2. Find Regional preferences. 3. Choose the country or region, currency, timezone, and language or date format that match your work. 4. Save changes. 5. Refresh any open packet, storefront, invoice, or shared workspace tab so generated displays use the latest preference.
Mosari is localization-ready but fallback-only for launch. This means key app responses, generated artifacts, Storefront inquiry messages, workspace messages, email-ready notification records, and Ask Mo responses carry localization context, but the visible copy still falls back to approved launch English until translated copy and provider/runtime checks are verified. If a page promises live multilingual support, report it as Feedback.
Publish from VendorOS storefront tools after your profile content is ready. 1. Sign in to Vendor Dashboard. 2. Open Storefront / Website builder. 3. Add services, packages, media, and FAQs you want public. 4. Preview the public page. 5. Publish and test the inquiry form from an incognito window.
Marketplace visibility depends on verification, audience settings, and publish state. 1. Confirm Marketplace Approved / verification status in VendorOS. 2. Check wedding vs event audience selection. 3. Confirm the marketplace profile is published. 4. Wait a few minutes and hard-refresh the marketplace page. 5. Email support@mymosari.com with your vendor business name if the profile should already be live.
Storefront inquiries can carry service, package, and event context into VendorOS as leads, customers, jobs, invoices, and shared workspaces.
Open Storefronts to view storefront marketing, or open Vendor Storefront to manage a vendor storefront. Storefronts present services and capture inquiries that flow into VendorOS.
Storefront inquiries can become VendorOS leads with service, event, customer, and message context attached.
Yes. Vendors can update storefront content, service details, forms, and public profile information from VendorOS when those tools are enabled.
Try these steps: 1. Open Vendor Storefront. 2. Confirm the change was saved. 3. Confirm the storefront is published, if publishing controls are available. 4. Refresh the public storefront page. 5. Confirm you are viewing the correct storefront URL.
Open Vendor Storefront. 1. Set up storefront profile details. 2. Configure the inquiry form. 3. Add services, packages, media, and public profile details. 4. Test the public inquiry form. 5. Confirm the submission appears in Vendor Leads.
Open Vendor Catalog and Vendor Storefront. 1. Create services and packages in Catalog. 2. Mark the public items you want to show. 3. Review storefront sections and inquiry form fields. 4. Save storefront changes. 5. Open the public storefront and confirm the services, packages, FAQs, and inquiry path read correctly.
Check these items: 1. Confirm the service or package is active. 2. Confirm it is marked public if public controls are available. 3. Confirm the storefront section that displays it is enabled. 4. Save the storefront again and refresh the public page. 5. If the item still does not appear, submit Feedback with the item name and storefront URL.
A storefront inquiry can create a VendorOS lead with the submitted customer details, event context, requested service, message, and source information. Vendors should review new leads before converting them into customers, jobs, quotes, or workspaces.
Marketplace audience marks whether a vendor should appear for weddings/couples, events, or both. Wedding marketplace views should include wedding and both-audience vendors. Event marketplace views should include event and both-audience vendors. General storefront marketplace views can show all vendors with filters.
Choose the audience that matches the services you can confidently fulfill. 1. Choose wedding if the service is built specifically for couples and wedding planning. 2. Choose event if the service is for corporate, nonprofit, private, production, or hosted events and should avoid wedding-specific copy. 3. Choose both only when the vendor can serve both markets with accurate portfolio, package, and inquiry details. 4. Review public profile copy after saving the audience.
Check the public status, verification state, and marketplace audience. 1. Confirm the vendor profile is public or marketplace approved. 2. Confirm the audience includes the marketplace being viewed. 3. Confirm the service category and location filters are not hiding the profile. 4. Refresh the page and test with All marketplace vendors. 5. Submit Feedback with the vendor name and marketplace URL if it is still missing.
The storefront builder should help service vendors present brand, portfolio, services, packages, testimonials, FAQs, availability, inquiry forms, marketplace readiness, SEO, domain status, and analytics readiness. It should not behave like a shipping, tax, inventory cart, or active checkout system in this pass.
High-end templates are preview catalog concepts right now. 1. Review the coming soon cards in the website or storefront builder. 2. Use standard selectable templates for active publishing. 3. Treat request-this-template actions as interest signals until template checkout and activation are approved. 4. Do not promise paid template access until the catalog release is live.
Premium and high-end templates are prototype previews in this release slice. They are intentionally not selectable until the template catalog, activation rules, and billing gates are finished. Use a standard template for live publishing.
Start from vendor signup, then finish business setup. 1. Open Vendor Sign Up or Create Mosari Account. 2. Create your Mosari account with the email you use for the business. 3. Continue into Vendor Dashboard. 4. Complete verification, services, and storefront setup. 5. Review Vendor Billing for plan access.
Open Calendar from the Vendor dashboard to manage appointments and job dates. 1. Go to Vendor Calendar. 2. Review upcoming events and job-linked dates. 3. Add or edit appointments when your plan allows it. 4. Connect calendar import/export tools if shown for your account. 5. Keep customer and job records linked so calendar items stay accurate.
VendorOS centralizes leads, customers, quotes, invoices, jobs, storefronts, billing, verification, and marketplace readiness.
Open Vendor Dashboard to manage leads, customers, quotes, invoices, jobs, storefronts, verification, billing, and reports.
A lead can be reviewed, followed up on, converted into a customer, and connected to quotes, invoices, jobs, or shared workspaces.
Vendors can create quotes for services and convert accepted quotes into invoices so pricing, payment status, and customer records stay connected.
Verification protects marketplace quality. Vendors may need business details, service areas, portfolio information, Stripe setup, and review before becoming marketplace approved.
Marketplace Approved means the vendor has completed the required verification and review steps needed to appear publicly and receive marketplace bookings.
Open Vendor Billing to review plans, subscriptions, credits, invoices, and billing portal access when available.
Try these steps: 1. Confirm you are signed in at Vendor Login. 2. Open Vendor Dashboard. 3. Check whether the page requires a vendor role, verification step, billing access, or workspace permission. 4. If access still fails, use Feedback from that page and include the action you expected to take.
Open Vendor Verification. 1. Complete basic business details and service areas. 2. Add a website or social profile. 3. Upload portfolio or service examples. 4. Complete Stripe onboarding when required. 5. Finish verification requirements. 6. Request marketplace approval when the checklist is ready.
Open Vendor Leads. 1. Open the new lead. 2. Review the request, event details, customer message, and source. 3. Add notes or follow-up tasks. 4. Respond to the customer. 5. Convert the lead when it becomes a real opportunity.
Open Vendor Customers to review direct clients, corporate accounts, storefront inquiries, marketplace customers, and Mosari Weddings couples connected to your vendor account.
Open Vendor Customers. 1. Choose Add customer. 2. Enter the display name, contact details, customer type, and source. 3. Save the customer. 4. Open the customer profile. 5. Add events, appointments, quotes, invoices, files, portal invites, or notes as they become relevant.
Try these steps: 1. Remove a trailing slash and open Vendor Customers. 2. Refresh the page once. 3. Sign out and back in at Vendor Login. 4. If only one customer record fails, open another customer to compare. 5. Submit Feedback with the page path, time, and whether the table or a customer profile failed.
Open Vendor Contracts to track draft, sent, signed, and countersigned agreements connected to jobs, customers, quotes, and uploaded document URLs.
Open Vendor Contracts. 1. Choose New contract. 2. Add the title and connect the customer or job when possible. 3. Set the status, such as Draft or Sent. 4. Add notes or a document URL if the agreement lives outside Mosari. 5. Save, then confirm the contract appears in the filtered list or related job.
Open the related job in Vendor Jobs. 1. Open the Contract tab. 2. Choose Add contract record. 3. Confirm the title, customer, job, and workspace context. 4. Save the record. 5. Return to Vendor Contracts to review all agreement statuses together.
Use the canonical route Vendor Contracts. Older saved links may have routed Contracts back to Jobs. Refresh the vendor dashboard navigation, then open Contracts again. If the issue continues, submit Feedback with the exact URL you clicked.
VendorOS is designed as a connected operating system. Leads can convert to customers or jobs, jobs can hold quotes and contracts, accepted quotes can become invoices, and invoices can track manual payments until online payment runtime is active.
Use this flow: 1. Open Vendor Leads and review the inquiry. 2. Convert the lead into a customer or job. 3. Create a quote from the job or Quotes page. 4. Add a contract record when the client is ready to book. 5. Create an invoice and record payment milestones. 6. Use the customer workspace or workflow view to keep tasks, files, and updates attached.
Check the record linkage: 1. Open the job and review Quotes, Contract, and Payments tabs. 2. Open the standalone Quotes, Contracts, or Invoices page and filter by job when available. 3. Confirm the record was created with the correct job ID or customer. 4. If the record is missing only from one view, submit Feedback with both record IDs and the job title.
Use this order when the tools feel disconnected: 1. Open Vendor Leads for a new inquiry. 2. Convert the inquiry into a Customer. 3. Create or connect a Job for the booked event or service. 4. Open Customer Workspaces for shared planning, files, and collaboration. 5. Open the Production timeline to build the minute-by-minute run of show across one or more days, assign vendors and customer contacts, add notes, and prepare packet shares. 6. Track quotes, contracts, invoices, and payment status from the job or their standalone pages.
Open VendorOS Guides from the sidebar. The guide page explains how Customer Workspaces, Customer Workflow, Customers, Planning Projects, Jobs, Storefront, Quotes, Contracts, Invoices, and Timelines connect.
VendorOS customer workspaces organize a vendor-client relationship into a shared working area. Depending on the source, a workspace may be a wedding workspace, event workspace, or vendor-client workspace with tasks, files, messages, invoices, and relationship context.
Open Customer Workspaces. 1. Search by customer or event name. 2. Filter by workspace family if needed. 3. Open the matching workspace card. 4. Review linked customer and job records. 5. Use the workspace links instead of copying standalone records when asking a customer or collaborator to review something.
A workspace may be missing if the customer was imported before workspace routing existed, if the customer was created without enough context, or if the source channel does not create a workspace automatically. Create or update the customer from VendorOS, then submit Feedback if the workspace still does not appear.
Open Customer Workspaces, choose the wedding, event, or vendor-client workspace, then select Open timeline on the card or workspace header. The Production timeline module is a minute-by-minute run-of-show editor where you can add multiple days, activities, start/end times, notes, lead owners, assigned vendors, assigned customer contacts, visibility, status, comments, readiness checks, and packet share history.
Open the Customer Workspace, select Open timeline, add each event day, then add activities in the order they should happen. Use start/end times for precise schedule rows, the optional time label for broad windows, lead owner for the person accountable, assigned vendors for teams doing the work, assigned customer/client contacts for people who need visibility, and notes for cues, dependencies, setup details, music, or handoff instructions. Use status and visibility to keep draft, vendor-only, client-visible, and completed rows clear before recording packet shares.
Open Vendor Developer to manage API readiness, API keys, webhook definitions, custom fields, and operational reports when those tools are enabled for the vendor tier.
Open Vendor Developer. 1. Review the current developer status. 2. Create or rotate API keys only when the integration is ready. 3. Register webhook endpoints with HTTPS URLs. 4. Test payload handling in a non-production workflow first. 5. Keep secrets outside screenshots, support tickets, and shared notes.
Developer tools may be gated by vendor tier, RBWA entitlement, or production readiness. Open Vendor Billing and Vendor Developer to confirm access. Do not paste secrets into Feedback; describe the endpoint, status code, and timestamp instead.
Marketplace approval requires the verification checklist and review steps to be complete. 1. Open Vendor Verification. 2. Complete missing business, service area, portfolio, and profile details. 3. Confirm any payment or KYC readiness fields are truthfully marked. 4. Request review when the checklist is ready. 5. If a completed item still shows incomplete, submit Feedback with the checklist item name.
VendorOS should keep the main business navigation, account identity, search, quick create actions, and workspace context available while individual tools load. Tool content can change, but the shell should not feel like a full app reload when moving between Leads, Customers, Quotes, Contracts, Invoices, Jobs, Storefront, Verification, or Settings.
Submit Feedback with the exact VendorOS route and what you clicked. 1. Include whether the sidebar or top bar disappeared. 2. Include whether the tool showed a loading state, blank state, or error. 3. Include the account type and whether a customer, job, or workspace was open. 4. Add a screenshot if spacing, overlap, or mobile behavior is part of the issue.
First confirm the tool has a live backend contract. Some polish surfaces may preview drawer behavior before every save path is active. If a save button is enabled and still fails, refresh once, retry with a small edit, then submit Feedback with the route, record type, field name, and any visible error.
Try these checks: 1. Confirm you are using a supported browser such as Chrome, Edge, or iOS Safari. 2. Confirm the site has finished loading and you are online. 3. Use the Install Mosari App button to open manual device steps. 4. If the app is already installed, the browser may hide the native prompt. 5. Refresh once or open the same dashboard in a new tab if the prompt still does not appear.
Open Vendor Settings. 1. Find Enable push notifications. 2. Confirm your plan is VendorOS Pro or higher. 3. Select Enable push. 4. Allow browser notifications when your browser asks. 5. Return to Settings to confirm the status shows enabled.
Check these items: 1. Confirm the browser supports notifications and Push Manager. 2. Confirm notification permission was not denied in browser settings. 3. Confirm your VendorOS tier is Pro or higher. 4. Confirm Mosari push runtime keys are configured for the environment. 5. If the browser permission is denied, change it from the browser site settings and try again.
Mosari-managed storage is the default place for uploads, generated packets, storefront media, thumbnails, exports, and files Mosari must serve. Google Drive BYOS stores selected-file references only. Google Drive files do not count against Mosari storage unless Mosari imports, copies, converts, thumbnails, scans, or republishes the file into Mosari-managed storage.
Free vendors can add manual external links. Launch vendors can use one Google Drive connection for selected file references on customers, jobs, and workspaces. Pro expands Drive attachments across Sales Documents, shared workspaces, packets, and VendorOS records. Studio supports team-ready Drive usage with multiple staff-connected accounts. Enterprise storage and provider policies are custom.
Google Drive BYOS references files where they already live. Mosari storage usage increases only when Mosari imports, copies, converts, thumbnails, scans, or republishes a Drive file into Mosari-managed storage. If a Drive connection or attachment is unavailable, check your tier, browser permission, and provider authorization state before retrying.
Open the Wedding Dashboard to manage budget, guests, vendors, seating, layout, registry, website, and planning progress from one workspace.
Create a free wedding workspace and plan from one dashboard. 1. Open Wedding Sign Up or Create Mosari Account. 2. Create your account and verify email if asked. 3. Open the Wedding Dashboard. 4. Add guests, budget, vendors, website, seating, and layout as you go. 5. Invite helpers from the shared workspace tools when you are ready.
Open Budget. 1. Choose Add New Category. 2. Enter the category name. 3. Enter the allocated amount, including cents if needed. 4. Save the category. 5. Confirm it appears in the budget list before leaving the page.
Use the Feedback button on the login page and choose Login. Mosari will capture the exact domain and path so the support team can review the affected login flow.
Yes. Budget amounts, vendor costs, deposits, and remaining balances should support dollars and cents, such as 1150.50.
Open Guests. 1. Choose the import option that matches your file. 2. Upload the file. 3. Review the detected columns and field mapping. 4. Confirm the import. 5. Review imported households, RSVP status, and any skipped-row report before moving into seating.
Layout exports can include the visual layout and, when selected, the seating chart with assigned guests for placed seating objects.
Make sure each row represents one guest, names are split clearly when possible, RSVP status columns are consistent, and household names are only shared by people who should be grouped together.
Open Guests after your spreadsheet is ready. 1. Keep one guest per row. 2. Put first name, last name, household, email, phone, RSVP status, meal choice, and notes in consistent columns. 3. Avoid merged cells, blank header rows, and repeated header rows in the middle of the file. 4. Use the same spelling for RSVP values, such as Attending, Declined, Maybe, or Pending. 5. If household names are shared by unrelated people, add email, phone, or address details so they are not grouped incorrectly.
Open Guests and review the import result after the file finishes processing. 1. Check the rows marked failed or skipped. 2. Read the reason shown for each row, such as missing name, unsupported RSVP value, duplicate guest, or invalid file format. 3. Correct the source spreadsheet or adjust the detected field mapping. 4. Re-import the corrected file. 5. Confirm the final totals match the number of valid individuals and households you expected.
Try these steps in Guests: 1. Open the import error report and identify the failed rows. 2. Check whether those rows are missing first or last names. 3. Confirm duplicate detection is not matching unrelated guests with the same household name. 4. Make sure the RSVP status values are recognizable. 5. If a file has many guests, compare the expected count against Total Individuals after import and report any mismatch through Feedback with the file type and row count.
Households connect guests who should be managed together for invitations, RSVP review, and seating context. 1. Guests with the same clear household name can be grouped together. 2. Shared email, phone, address, or relationship fields can strengthen the match. 3. Missing emails should not automatically prevent a valid guest from importing. 4. Shared household names alone should not merge unrelated guests when other details conflict. 5. Review household totals after import before using the guest list for seating.
Use this checklist in Guests: 1. Review the source column used for RSVP status. 2. Normalize values like Yes, Attending, Accepted, No, Declined, Maybe, and Pending. 3. Avoid mixing notes with RSVP status in the same column. 4. Re-run the import with the corrected file. 5. Spot-check several guests in each status group before sending invitations or building seating.
Use WeddingOS after account creation. 1. Open Wedding Dashboard. 2. Complete onboarding details if prompted. 3. Add guests, budget, vendors, website, seating, and layout as needed. 4. Invite helpers through shared workspace tools. 5. Return to Mosari Platform only for account-wide membership or billing changes.
Open Layout Builder to create or edit tables and seating objects, then open Seating. Seating reads the layout objects so names, shapes, capacities, and placement status match the visual plan.
Yes. Seating is organized by layout area, so a guest can have a ceremony assignment and a separate reception table without creating a conflict.
Use Layout Builder as the source for physical tables and seating objects. 1. Create the layout area, such as Ceremony or Reception. 2. Add tables or seating-capacity objects. 3. Set each visible label and capacity. 4. Save the layout. 5. Open Seating and confirm the same objects, labels, shapes, capacities, and placement status appear.
Open Seating. 1. Expand the layout area you want to plan, such as Reception Seating. 2. Select a table or seating object. 3. Add guests from that area-specific unassigned list. 4. Watch the assigned count and remaining seats update. 5. Repeat for other areas. A guest can have one ceremony assignment and one reception assignment without conflict.
Check the connection between Layout Builder and Seating. 1. Confirm the table still exists in Layout Builder. 2. Confirm the visible label is the name you expect. 3. Save the layout after renaming, copying, deleting, moving, or resizing objects. 4. Refresh Seating and check whether stale copies disappear. 5. If a placed table still shows as not placed, submit Feedback from Seating and include the table label and layout area.
Open Seating and use the conflict panel when available. 1. Identify the affected layout area. 2. Check each table capacity and assigned count. 3. Move guests from over-capacity tables to tables with remaining seats. 4. Add another table in Layout Builder if the room needs more capacity. 5. Re-check area-specific unassigned counts before exporting.
Seating rules are meant to protect the plan during manual and automatic assignment. 1. Rules can keep households together, avoid seating certain guests together, prioritize VIPs, and respect table capacity. 2. If a manual placement violates a rule, review the warning before saving. 3. Choose an override only when you intentionally want to break the rule. 4. Review suggested seating when the system offers a better placement. 5. Re-run conflict checks after changing rules or assignments.
Open Layout Builder. 1. Confirm the layout objects, labels, sizes, and capacities look correct. 2. Choose Export PDF or Print. 3. Select whether to include the seating chart. 4. Review the generated layout before sharing or printing.
Labels are what couples and guests recognize. Seating exports and charts should use the visible label so printed documents match the planner view.
Open Layout Builder. 1. Create layout areas that match the venue, such as Ceremony and Reception. 2. Add objects one at a time and keep them inside the canvas. 3. Use visible labels that should appear on printed documents. 4. Set capacity on tables and seating objects before opening Seating. 5. Export a test PDF and confirm shapes, labels, rotations, and capacity counts match the builder.
Use the object controls in Layout Builder. 1. Select the object you want to adjust. 2. Set width and length using the dimensions controls when available. 3. Drag resize handles for visual adjustments. 4. Use rotate handles for angled placement. 5. Confirm the label remains readable after rotation and that the object does not overlap nearby tables or walkways.
Check these items in Layout Builder: 1. Confirm the object shape is correct before exporting. 2. Confirm width, length, rotation, and capacity are saved. 3. Make sure the export is using the visible label, not an internal linked name. 4. Do not include unplaced seating objects in the export. 5. If rectangles export as circles or sizes change, submit Feedback with the layout name and exported PDF.
Use this order before opening Seating: 1. Build the physical room in Layout Builder. 2. Name each table with the label guests and staff should see. 3. Set capacity for every seating object. 4. Place each object in the correct layout area. 5. Save the layout, then open Seating and confirm the objects match one for one.
Open Website Builder to publish event details, schedule information, RSVP access, registry links, guest information, and selected planning content based on your privacy settings.
Open Registry to manage registry links and cash-fund options. Cash funds let guests contribute through Mosari-supported registry payments, with fees and payment details shown before checkout.
Open Vendors to track each wedding vendor, booking status, contact details, payment context, notes, files, and workspace handoffs. Vendor records should support budget review, layout/setup notes, shared workspace access, and day-of packet preparation.
Use the Vendors tool before exporting packet details. 1. Confirm each booked vendor has a business name and primary contact. 2. Add arrival, setup, meal, payment, and venue notes where relevant. 3. Attach or link contracts, invoices, and reference files. 4. Confirm which vendors need shared workspace access. 5. Review the packet preview to make sure vendor details appear in the correct section.
Check the vendor source record first. 1. Confirm the vendor is saved in Vendors. 2. Confirm booking or visibility status is set correctly. 3. Confirm files, payment notes, and setup notes are attached to the same workspace. 4. Refresh the target workspace or packet preview. 5. Submit Feedback with the vendor name, workspace, and missing packet section if the source record is saved but absent.
Try these steps: 1. Wait a few seconds for the action to finish. 2. Do not click the same button repeatedly while it is processing. 3. Refresh the page and try the action again once. 4. If it still fails, use Feedback from that page and include the button name, what you expected, and the page path.
Open Guests. 1. Add guests manually or import a guest spreadsheet. 2. Review household grouping so partners, families, and shared invitations are connected correctly. 3. Confirm RSVP fields and meal or attendance details if you are collecting them. 4. Use filters above the guest list to find missing details. 5. Resolve skipped or failed import rows before using the list for seating or invitations.
Use this workflow: 1. Open Layout Builder and build the room. 2. Add table or seating objects with clear labels and capacities. 3. Open Seating. 4. Choose the layout area, such as Ceremony or Reception. 5. Assign guests to each table or seating object. 6. Review conflicts and unassigned guests for that area. 7. Export the seating plan when assignments are ready.
Open Layout Builder. 1. Confirm each object is named with the label you want printed. 2. Confirm seating assignments in Seating. 3. Choose Export PDF or Print. 4. Turn on Include Seating Chart if you want guest lists attached. 5. Review the generated packet before sending it to a planner, venue, or vendor.
A planning packet is a consolidated export of the details a planner, venue, vendor, or day-of lead needs. It can include timeline notes, layout and seating, vendor details, guest or RSVP summaries, files, and custom fields when those export tools are enabled.
Use this checklist: 1. Confirm guests and RSVP responses are current. 2. Confirm seating assignments and layout labels are final. 3. Review vendor records, contact details, arrival notes, and payment status. 4. Review schedule, travel, and website FAQ content. 5. Add custom notes or fields that your planner, venue, or vendors need before exporting or emailing a packet.
Check the source records before exporting: 1. Confirm the data is saved in the relevant workspace section. 2. Confirm hidden or private fields are meant to be included. 3. Confirm RSVP and seating data are attached to the same workspace. 4. Refresh the page and regenerate the packet. 5. Submit Feedback with the packet type and missing section if the source data is saved but absent from the export.
Ask Mo is Mosari help inside the app. Mo reads the current product, page, section, FAQ entries, How-To guides, and Technical Support articles before answering. Use Mo for quick guidance, then open the linked article or submit Feedback when the help library is missing something.
Use the small Ask Mo tab when the assistant is collapsed. 1. Select the Ask Mo tab at the edge or bottom of the browser window. 2. Ask a specific question about the page you are on. 3. Review the matched FAQ, How-To, or Technical Support result. 4. Open the full article when the answer says more detail is available. 5. Submit Feedback from the same panel if the answer does not cover your workflow.
Try these steps: 1. Use the collapse or hide control to move Mo out of the way. 2. Refresh the page once. 3. Check whether the issue happens on mobile, desktop, or both. 4. If Mo still overlaps a CTA or link, submit Feedback with the page path, device size, and the button being covered.
Use the Install Mosari App button from your dashboard when it is available. 1. Open the Wedding Dashboard, Events Dashboard, VendorOS, or Marketplace in your browser. 2. Select Install Mosari App. 3. If the browser shows a native install prompt, confirm it. 4. If you are on iPhone or iPad, use Safari Share, then Add to Home Screen. 5. Open Mosari from the new home-screen icon.