Platform flexibility: what can change, and how far
Six layers of Mako can be shaped to your business. Here is what each one means in practice.
Six layers
Where the platform bends
Your language
Stages, categories, statuses, lead sources, next actions and menu titles.
Your structure
Parents and children, locations, chapters, partners and which views exist.
Your behavior
Which stage changes start which work, with approvals and a switch on each automation.
Your channels
Calls, texts, mailboxes, e-mail campaigns and social pages, each on your accounts.
Example scenarios
What customization looks like in practice
Scenarios are illustrative. They show what the platform can be configured to do.
Renaming the funnel
A property manager can rename “Prospect” to “Inquiry”, add a “Showing booked” outcome and a Showing stage, and have the call queue use those words.
Tying stages to work
A distributor can configure “Prepare proposal” to draft a proposal and cover e-mail, and “Collect signatures” to send a signature request, each with its own switch.
Limiting what volunteers see
An association can give a chapter's volunteers access to their own chapter's records and nothing else.
Pausing while you test
A multi-location retailer can leave outbound e-mail switched off while its templates are reviewed, then turn it on for one job at a time.
See it change
Three configurations, one platform
Inquiry
Showing
Application
Lease signed
Move-in
Quote requested
Quoted
Order placed
Installed
Serviced
Inquiry
Chapter assigned
Agreement sent
Member
Renewal due
Example configurations with sample data.
Honest limits
Flexible is not the same as unbounded
Configuration covers a great deal, but not everything. A new integration, a new kind of record or a data migration is a separate piece of work. We tell you early which category a request falls into.
Bring a process that does not fit a template
We will show how the platform could bend around it.