Skip to content

Workflow guide

Support plan for SaaS teams

Answer setup, feature, and plan questions from your docs and changelog. Account changes, security issues, and billing exceptions stay with your team.

Build an agent for freeCheck available integrations

What the visitor sees

Questions to test

What the agent answers, and what stays with your team.

Use these questions as test prompts. Each one should be answered from the source under it. Account-specific answers need authentication and a supported connection.

Product help

Planning sample

Answer from approved sources

  1. 01
    Where do I find my API key?Help docs
  2. 02
    Which plan includes audit logs?Plan comparison
  3. 03
    What changed in the last release?Changelog
Boundary

Hand to your team

  • Trial extensions, credits, and billing exceptions
  • Account ownership and security changes
  • Bug reports that need an engineer
For example
Can you extend my trial by another two weeks?
Planning guide. The examples on this page help you scope a test. They do not mean every provider, data source, or action is already connected.

Handoff rules

Write down where the agent stops.

When it does, your team sees the whole chat, not a summary.

  1. 01

    A request to change the account owner

    Ownership changes need an identity check, so the agent hands the chat to your team.

  2. 02

    A double charge or billing error

    The agent creates a support ticket with the conversation attached.

  3. 03

    A bug the docs don’t cover

    The agent says so and passes the chat to support instead of guessing a workaround.

Not every job belongs to an agent. Emergencies, licensed advice, and decisions nobody has approved stay with people. See the stop conditions

What your team sees

A safer first version

Four steps, one pilot review.

Record a baseline before the test, use the same time window after it, and keep the result tied to your own conversation data.

  1. 01Choose one support job
  2. 02Add approved sources
  3. 03Set action and handoff rules
  4. 04Run a private test

Sample measurement checklist

Pilot review

Pilot review progress: 0/4

Questions before setup

Decide the rules before customers see it.

Yes. Add each page as a website link. The source list shows each page’s status, and every answer cites the page it came from.

No. Agents can’t run billing actions. Plan changes and credits go to your team through a handoff or a support ticket.

Account-specific lookups and actions in another system need a supported integration and the right permissions. Check the integrations directory before including either in the workflow.

Use real questions with sensitive data removed. Compare each answer with the approved source, test the handoff, and record any missing or incorrect answer before making the agent public.

More workflow guides

Plan another support job.

All solutions

Test one narrow workflow first.

Start with five real questions, remove sensitive data, and compare every answer with the source your team approved.

Build an agent for freeTalk through your workflow

No credit card required