Separately agreed after the pilot. Includes a weekly routing check, a monthly exception summary and up to one hour of minor rule or field changes per month.
Additional work is quoted separately. This is not round-the-clock support or a response-time guarantee. Platform subscriptions, usage charges and taxes are separate.
When the starting scope does not fit
Multiple forms, custom APIs, historical migration, complex routing, regulated records or unsupported connectors need a separate assessment and quote.
WHAT YOU RECEIVE
A workflow your team can operate.
1. Map the actual handoff
Identify the form owner, required fields, destination, assignment rules and fallback person. Confirm permissions and connector support before live access.
2. Build a controlled pilot
Validate required fields, map the enquiry, assign an owner and put incomplete or unrecognized records into review. Keep a manual fallback available.
3. Test the exceptions
Test a valid enquiry, a repeated submission, missing contact details, an unknown category and a destination outage. Document the expected result and recovery action.
4. Approve the handoff
Review the test evidence, operating instructions and responsibilities. Live activation follows your approval of the agreed scope and access.
This example uses fictional records in this browser only. It does not send messages, connect to your CRM or create a lead.
Choose an example and run it to see the expected routing result.
Decide whether this is the right first project.
Who is a good fit?
A business with a working web form, an existing enquiry destination and someone responsible for follow-up. You should be able to explain who handles each category and what happens when the destination is unavailable.
Does the pilot include a new CRM or automatic sales outreach?
No. It connects a defined enquiry source to an agreed destination. A new CRM, outbound sales campaigns, SMS, AI qualification and automatic acceptance or rejection of customers are outside this starter scope.
Which tools can you connect?
We confirm the exact form, destination, connector, fields, permissions and plan limits during assessment. A platform appearing in an integration directory is not a guarantee that it supports your required operation. Make or another suitable platform may be considered after the workflow is understood.
How long does it take?
A delivery date is agreed after reviewing your current setup and access requirements. Delays in permissions, connector support or third-party systems can change the schedule.
What counts as a successful pilot?
The agreed test cases pass, each valid enquiry reaches the correct destination and owner, failures have a documented recovery path, and your team receives the handoff instructions. No sales, savings or conversion result is guaranteed.
AutomateRite