Explain your public services
Publish practice areas, office information and the way to request an initial conversation. AI should not invent advice or promise representation.
Organize public service inquiries and callback requests so the right person can handle intake. Keep legal advice and engagement decisions with the firm.
A prospective client asks whether the firm handles a type of matter and later phones the office. Staff can continue the inquiry with the earlier context in view.
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.
Publish practice areas, office information and the way to request an initial conversation. AI should not invent advice or promise representation.
Guide the visitor to the firm’s chosen intake process. Avoid asking for detailed confidential case information in a public support channel.
Share the request with the appropriate colleague and include the conversation link. Conflict checks and engagement decisions remain with authorized staff.
Use an internal follow-up for a promised callback. Acknowledging or completing the task stops unnecessary reminders.
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.