Qualify the request
Collect the service needed, the area and the best way to reach the customer. Explain your approved service coverage before promising a visit.
Keep job inquiries, booking requests and follow-up calls connected so your office and field team can work from the same request.
A customer describes a leaking tap online and calls to clarify access instructions. Keep both conversations available to the colleague arranging the visit.
Related history and a shared working Inbox help the team pick up the request with context. Internal Team conversations keep colleagues close to the answer.
Explore this part of Message →Build around the requests your team already handles. Start with the knowledge, channels and handoffs that make those conversations easier.
Collect the service needed, the area and the best way to reach the customer. Explain your approved service coverage before promising a visit.
Use the service durations, capacity and availability configured by the business. Let a person handle emergencies or jobs that need an assessment.
Record useful customer-provided instructions in the conversation. Avoid putting private access information into public knowledge articles.
Assign questions or callback promises to the right teammate. An internal AI nudge can help the owner remember the next step.
Scan your website or answer the onboarding interview. Review the drafts, publish approved answers and set company-specific guidance for AI. Connect only the sources that belong in this workspace.
See how Message AI learns →Choose connections for your workflow. Open each guide to see its actual capabilities, required permissions and setup.
Connect one channel, publish a small set of approved answers and invite the people who will use the workspace. Test the experience from both sides of the conversation.
No. Build its knowledge from your approved information and connected sources. Review generated articles, configure company guidance and test your actual questions before enabling customer-facing replies.
Yes. Your team can handle requests that need judgment, authorization or information AI does not have. Use assignments, internal discussion and customer history to give the next person the context.
No. Read-only connections provide permitted information; they do not authorize refunds, cancellations, account changes or other actions. Check each connector’s capabilities and keep decisions with the appropriate person or system.
Chat, Tickets or Phones start at $5/month each with five human support agents included. Support is $10 and Business is $15. Additional services, AI add-ons and usage can be charged separately. The pricing page explains the starting costs.