Skip to main content

Appointment requests

Collect the request. Keep confirmation with your team.

Answer service questions and gather appointment preferences through WhatsApp or API chat for human follow-up.

01

What you can configure today

WhatsApp and authenticated API chat, with your knowledge, permitted tools and team.

  • Answer from your knowledge

    Add service information, booking-request instructions and preparation guides.

    • Add documents or URLs
    • Link the knowledge base to an agent
    • Set instructions for the questions it should handle
  • Track requests and handoffs

    Record the requested service and preferred time in a ticket for your team to review.

    • Define ticket fields and status
    • Assign work to your team
    • Keep the conversation available for follow-up
  • Connect context you control

    Configure HTTPS customer-data endpoints or approved MCP tools when your process needs external information. Agent access, customer identity and permissions still apply.

  • Confirm the workflow scope

    A recorded request is not a confirmed appointment. Calendar availability, booking or rescheduling actions require a configured, authorized tool.

02

From question to follow-up

A sample conversation, not a customer testimonial or a measured outcome. Your knowledge and configuration determine the actual response.

Chapter 01

Keep the next step visible

Answer the question the knowledge supports, then route any request that needs a person.

  • The agent uses the sources and tools you enable.
  • A teammate handles work outside the configured automation.

Match the product to your process.

Discuss your current requirements with our team. Additional channels and native business-system connectors are planned separately, with no release dates promised.