The Marketplace contains messaging flows, voice IVRs, and bundles created for reuse. Use it when an existing appointment, enquiry, or order-taking flow could save your team setup time.
For example, a clinic could preview an appointment flow, obtain a copy, then replace its wording and connect the clinic's own channels before publishing.
Check access and fit
Open Marketplace. Viewing and purchasing are separate permissions; buying or installing requires marketplace purchase access. You also need access to the relevant flow or IVR builder to configure the result. Paid purchases use an order, so the person completing payment needs catalogue order access and management permission for payment actions.
Search by the business problem, then narrow the results with Messaging, Voice IVR, Bundles, a category, or Free. Open a listing and check its price, currency, version, licence, seller, and required connections.
Use The graph to inspect step types and branches. The seller may leave some content locked, so an outline is not necessarily the complete configuration. About explains the solution and what you must connect after installation. Reviews contains buyer feedback.
Where available, select Try it first or Try it. Use the messaging choices or IVR keypad to explore more than one path. The demo is a simulation; it does not establish that your own numbers, payment provider, or customer handoff settings are ready.
Obtain the solution
- For a free listing, select Get it. Momo adds it to My purchases without a payment checkout. Installation is still a separate step.
- For a paid listing, check the displayed one-time price and select Buy and install. This raises an order and opens its detail page; it does not immediately install the solution.
- Check the order's title, amount, and currency. Complete payment using an available method under Collect payment.
- Return to My purchases and check the state. Waiting for payment is not ownership ready for installation. Paid — not installed yet makes Install available.
- Select Install and open the resulting draft to configure it.
A new marketplace order may have no customer chat. In that case, Request payment cannot send choices. If mobile money collection is configured, use Or choose a method for them, select Mobile money prompt (PIN on their phone), enter the payer's Phone, and choose Send directly. Payment still needs provider confirmation.
The purchase payment is separate from your Momo service-credit top-up. Obtaining a flow does not include the future messaging, voice, or AI usage it may generate; check Billing for those service costs.
Configure the draft before publishing
Installation creates editable copies from the purchased version. Review customer-facing wording, conditions, destinations, and error paths. Connect your own numbers, channels, and other required resources, then test the relevant branches before publishing.
Find messaging copies in Flows and voice copies in IVRs. If a purchase's IVR shortcut fails to open, use the IVRs list and search for the installed name.
Follow the message-flow guide or IVR guide for the next setup steps.
Resolve purchase and version questions
If payment remains waiting, compare the order's payment attempts and reference before retrying. If the order says paid but the purchase stays waiting, provide both records when requesting help. Do not buy again to repair the state.
There is currently no marketplace upgrade action for replacing an installed copy with a seller's newer version. Your edits remain your responsibility; a listing update does not automatically update them. The buyer screens also have no self-service refund form, so request help with the purchase and error details rather than treating a status change as a refund.
Review the installed copy as a new workflow
After installation, list everything the solution expects your business to supply: greeting text, working hours, recipient destinations, product references and any connected tools. Replace sample values before testing. A demo can show a convincing journey while still using example data that does not belong to your workspace.
Walk through a successful request, invalid input and a human handover. Check where information is stored and what happens when a lookup finds nothing. For a voice IVR, test the live destination after publishing; for a message flow, test from the intended connected account.
Keep the purchased version and your local changes distinguishable in your team's notes. This makes a later support discussion more precise: state whether the problem happens in the original design, the configured copy, or a connected service.
Before another teammate maintains the flow, show them its entry point, fallback and publishing process. Installing a solution saves design work, but someone in your business still needs to own its day-to-day behavior.