How can we help you?

Phone Calls on Rails: Deciding What Is Fixed and What the Bot Decides

Use this when a customer asks how to set up their phone line, voice bot or any call flow so it behaves the same way every time, or when you propose a workflow for a phone line. The principle: anything that changes data, sends something, moves the caller or keeps time is done by a skill or a fixed step, never by wording in the bot's instructions. The bot's wording only decides how to say it.

What belongs in a fixed path (code, skill or workflow step)

Situation Fixed path Why
Transfer to a person A transfer step that checks business hours and whether the team is available, then dials the configured number; outside hours it goes to the callback or ticket step A bot can promise a transfer that cannot happen
Send a link or steps by text The text-link skill; the destination is always the number the caller phoned from The bot cannot send to a third party or invent a link
Book, move or cancel an appointment The booking or calendar skill for the connected calendar (Velaro scheduler, Calendly, Outlook, Acuity and others). Times come only from the skill's open-slot lookup Calendars change by tool call, never by what the bot says
Create a ticket or callback The ticket skill. It requires an email on file or an explicit decline, and refuses a second ticket on the same call; changes go to the note or update skill Prevents duplicates and tickets nobody can answer
Hours and closed messages Read from the line's business hours, always with the timezone Never typed into instructions
Goodbye and hang-up A fixed rule on the caller's words, not the bot's judgment A bot can hang up on a request that follows "that's all"
Identity before account details The identity step, then the lookup skill Never answer account questions on a guess

What the bot decides

Greeting wording, how to explain a product, how to ask one short follow-up, how to confirm back what a skill returned. Keep every spoken answer to two short sentences.

How to build a call flow on rails

1. Write the steps a caller can take (get info, get a person, leave a message, book, check status).

2. For each step, name the skill or fixed node that does the action. If none exists, ask for it to be built; do not describe the action in the bot's instructions.

3. Put the order of steps in a workflow with branches (open or closed, found or not found, confirmed or declined) so the route is the same each call.

4. Let the bot hand data into the step (name, email, topic) and read the result back in plain words.

5. Test with a real call: ask for a person, a text, a booking, a change to the booking and a ticket, and confirm each result in the product (text delivered, call leg placed, calendar entry changed, ticket created once).

Orchestrating back and forth

When the caller changes their mind mid-flow ("actually move it to Friday"), the flow goes back to the lookup step, offers new times from the skill, and updates the same record instead of creating a new one. Offer a text confirmation only after the booking skill reports success.

Limits and availability depend on your plan; see your plan under Billing, Usage Overview.

Share: Email

Was this article helpful?