A modular business workspace
Your way of working belongs here.
Choose the parts of mCRM that help, keep supported tools you already use and decide who sees what. Start with a useful connection and grow from there.
Choose what you need
Choose an area to start.
Switch business areas on and off in the example. Your working setup changes with your choices.
Supported account connections can bring your existing services into the workspace. Not every tool needs replacing.
Account scopes, role permissions and approval rules define what a person or connected tool can do.
Import, review and export the records you need. Supported incoming lead connections and scoped APIs link the next part of the business.
Module choices here are illustrative, not a subscription change. Connections need supported providers and authorization. General outgoing Webhooks/Zapier automation is not established by the current verified scope.
Explore the actions in this area
A shared business context. Your choice of tools, modules and roles.
Records
Keep customer, job and financial records available across the workspace.
- 01Open the customer record
- 02follow its related job
- 03inspect the financial records attached to that work.
Exports
Export business records for reporting, portability or further analysis.
- 01Choose accessible business records
- 02select the export scope
- 03use the file for reporting or portability.
Data catalog
Understand the fields behind your records and their access rules.
- 01Inspect the record type
- 02review its field definitions
- 03check access rules before building a data connection.
Connections
Manage account connections and permissions for supported external services.
- 01Choose a supported service
- 02authorize the correct account and scope
- 03inspect connection status and revoke access when needed.
Webhooks
Receive leads through a configured inbound connection. Availability of general outbound event webhooks needs confirmation.
- 01Configure the supported inbound lead endpoint
- 02deliver a sample enquiry
- 03verify the resulting lead and source. General outgoing events need separate confirmation.
Zapier & automations
Connect lead delivery from Zapier to the supported intake endpoint. Broader automation flows require a separate availability check.
- 01Choose the external trigger in Zapier
- 02map its lead fields to the supported intake
- 03verify delivery. Additional workflows require a compatibility review.
AI access
Let an authorized AI tool use scoped access, with approval required for designated actions.
- 01Authorize the AI connection with limited scope
- 02review its proposed action
- 03require approval where the action policy calls for it.
API keys
Connect your own software using keys restricted to the access it needs.
- 01Create a scoped access key
- 02connect your software to the permitted endpoints
- 03review access and revoke the key when no longer needed.
See where your day
could come together.
Explore the sample workspace, then talk through the setup your team needs.
Explore the demoTalk to us