What your implementation includes
Your written proposal identifies which deliverables belong in your scope and the acceptance criteria for each.
| Deliverable | What your team receives |
|---|---|
| Workflow map | The inquiry triggers, decisions, documents, owners and next steps for the chosen process. |
| Information and rules inventory | Approved rates, policies and information sources, with gaps and maintenance owners identified. |
| Approval rules | What the AI may draft or send, which changes it may apply, and when a person must decide. |
| Configured workflow | The agreed channels, templates and actions in Everybooking. Any integration work is explicitly scoped. |
| Test record | Representative inquiries, expected outcomes, actual results, exceptions and corrections before rollout. |
| Team training and handover | How to maintain information, review conversations, resolve exceptions and pause a workflow. |
You retain decisions about your business rules. The starting price does not include every channel, migration or custom integration. See implementation pricing.
1. Work through a complete inquiry
Bring a few real conversations, including the difficult ones. We look at what the customer asked, what information the answer needed, and what your team had to do.
A reply may need prices, availability, customer history, policies, a booking change or a new invoice. Together, we map the work and choose a useful starting scope.
2. Connect the information and define the rules
We identify the sources of your prices, inventory, customer details and operating policies, and confirm how the agreed setup can use them.
You decide the rules and boundaries: what the AI may prepare, what it may handle automatically, and which exceptions need a person. Your proposal identifies the channels, workflows and any additional integration requirements. See what affects cost.
3. Test the answer and the work behind it
A readable reply is only one acceptance criterion. Test the whole sequence against agreed examples before enabling automatic actions.
- Routine request: correct line items, units, amounts, inclusions and next step.
- Missing information: request the missing detail without inventing a price or confirmation.
- Changed request: recalculate the draft and preserve the original accepted scope until the required approval.
- Unavailable item or conflicting rule: explain what cannot be confirmed and assign the exception.
- Payment already recorded: keep the document, balance and reply consistent; no duplicate charge or unintended refund.
- Human handoff: the responsible person can see the issue and the customer has an accurate status.
The commercial quote revision and prioritized email example illustrate the kinds of cases we work through. Your own acceptance cases use your approved data and rules.
4. Launch the agreed workflows and train your team
The website’s Instant Quote button can be one entry point. Email, SMS and voice can be included according to the agreed implementation scope.
Your team learns how to maintain the information and rules, review conversations and manage exceptions. We agree the rollout schedule and any continuing support in your proposal.
What we need from your team
Bring your website, a few customer conversations, example quotes or invoices, and the rules your team follows. We also need someone who can approve business information and decisions about AI autonomy.
You do not need everything documented before the first call. Finding the gaps is part of understanding the setup.
What the free workflow discussion establishes
Bring one representative customer conversation and the work required to resolve it. During the free 30-minute discussion, we identify the likely starting workflow, information gaps, approval needs and whether an implementation is worth scoping.
The call is a fit and scope discussion. Detailed mapping, configuration, integration development and operational testing belong to an agreed paid engagement. You are not buying a completed business-wide audit by booking a call.
Professional implementation starts at US$5,000. Final pricing and timing follow the requirements review; software and any ongoing support are separate. You can explore the examples or use the proposal template before discussing your workflow.
