Connect

Concierge Actions

Actions turn a visitor's intent into a configured next step without copying provider, routing, video, or promotion settings into another workspace.

Open the public Actions directory for complete what-it-is, how-it-works, provider, placement, and setup guidance for every action.

Choose the customer outcome

  • Bookings: Help visitors choose a time or prepare a booking request.
  • Payments: Send visitors into a connected checkout or verified payment flow.
  • Promotions: Show an approved offer, announcement, coupon, or campaign message.
  • Videos: Play an overview, explainer, or contextual customer video.
  • Requests: Collect a structured service, support, quote, or lead request.
  • Call requests: Let visitors call now or leave details for a callback.
  • Messages: Start an email or Concierge conversation with the right context.
  • Human handoff: Route a visitor and their context to the right person or team.

Where configuration belongs

  • Actions shows readiness, customer visibility, provider, placements, and tests.
  • Integrations owns provider authorization and connection health.
  • Routing owns human delivery, notifications, and fallback destinations.
  • Site Settings owns promotion and video content.
  • Pages Studio and website triggers own placement.

Set up an action

  1. Open the site and choose Actions.
  2. Select the action and read its readiness message.
  3. Use Manage configuration to open the existing owning workspace.
  4. Add the action to the AI Agent, a Pages button, or an existing-website trigger where supported.
  5. Use Test action and confirm the customer destination before making it visible.

Understand readiness and visibility

Ready means required configuration checks passed. Customer visible means at least one supported placement can expose the action. A connected provider alone does not publish an action.

A verified PayPal, Square, Calendly, Cal.com, or Google Calendar link can be usable even while native provider execution is still in development. Stripe native checkout is a controlled beta.

When an action needs attention

  • Open the readiness message and follow its owning-workspace link.
  • Confirm the destination belongs to the business and uses HTTPS.
  • Check Routing when a request or fallback is not reaching the team.
  • Remove a placement if the customer path is not ready; do not substitute an unverified provider.