Skills

Real capabilities, with guided forms — never raw JSON.

Skills are what your agent can actually do: book the job, log the lead, transfer the emergency, notify the team. Each one is a short, friendly form — which means the owner can wire real work into the agent without an engineer in the room.

Free credits included. No credit card required.

Scripted demo — a replay of the real product, not a live session.

The catalog

Everything a good front desk does, as Skills.

Mix and match per agent. The same Skills answer on your phone number and in your website chat — configure once, live on both.

  • Book on a calendar

    Take appointments straight onto a Google Calendar — the caller leaves with a time, not a promise of a callback.

  • Log to a spreadsheet

    Write every lead or request into a Google Sheets row — time, name, number, and what they asked for.

  • Transfer the call

    Warm-transfer to a human with the context handed over — which means nobody repeats their story twice.

  • Send an email

    Notify your team the moment a call needs them: caller name, callback number, and the reason.

  • Send a text

    SMS notifications for the moments email is too slow — an after-hours emergency, a hot lead, a booked job.

  • Answer from knowledge

    Ground answers in your FAQs, docs, and site — so the agent answers from your content, not guesses.

  • Take a message

    When a human isn’t needed right now: capture name, number, and reason, and route it to the right inbox.

  • Look up a record

    Check a status, order, or reference by phone number or ID and read the caller the answer.

Guided forms

Two fields, not a config file.

This is the entire setup for calendar booking: pick the calendar, set the appointment length. The form asks for what it needs in your language and nothing more — which means adding a capability takes about as long as reading this paragraph.

And every Skill declares its data up front. Before you save it — long before a caller reaches it — you know exactly what it will send, and where.

Book on a calendar

Calendar

Google Calendar — Dispatch

Appointment length

60 minutes

Data that leaves

caller name, phone, requested time → Google Calendar

A recreation of the real Skill form — simplified for the page, true to the product.

Know what leaves your system.

See exactly what caller data each Skill sends out — before it ever goes live. It's printed on the Skill while you configure it, and listed again in the pre-publish report's "Data that leaves" section: Book appointment → Google Calendar: name, phone, time. Most platforms make you trust; Flowyte lets you check.

Pair it with Guardrails for what the agent may say, and the pre-publish report for the full pre-flight review — will say, won't say, and what data goes where.

Integrations

Google Calendar and Google Sheets, built in. Everything else, connected.

One org-level connection backs every Skill that uses it — link your calendar once, and any agent can book on it. For the rest of your stack, Skills connect through secure OAuth, webhooks, and the API — the same /api/v1 the dashboard uses — which means no waiting for a connector marketplace to catch up to your tools.

Tutorial: give your agent Skills

FAQ

Frequently asked questions

What are Skills in Flowyte?
Skills are the capabilities you give your agent — booking appointments, logging leads, transferring calls, sending email or SMS notifications, answering from your knowledge, taking messages, and looking up records. Each one is added with a short guided form, and the same Skills work on both voice and chat.
Do I have to write JSON or code to configure a Skill?
No. Every Skill is configured with a guided form — never raw JSON. A calendar booking Skill, for example, asks which calendar to use and how long appointments run. Developers who want programmatic control can manage the same Skills through the API.
Which integrations does Flowyte support?
Google Calendar and Google Sheets are built in. Everything else connects through secure OAuth, webhooks, and the API, so your existing systems can receive data from the agent and trigger actions without a prebuilt connector.
How do I know what data a Skill shares?
Every Skill declares exactly what caller data it sends out — for example, a booking Skill sending name, phone, and requested time to Google Calendar. You see it on the Skill itself while you configure it, and again in the pre-publish report’s "Data that leaves" section before anything goes live.
Can the agent hand a call to a real person?
Yes. The transfer Skill warm-transfers the call with context, so your team hears who is calling and why before they pick up. You decide when transfers happen — an emergency keyword, a caller request, or any rule you set.
Can developers build custom Skills?
Yes. Beyond the built-in catalog, custom capabilities connect through secure OAuth, webhooks, and the same /api/v1 the dashboard uses — so anything your systems expose, the agent can act on.

Hear a Skill do the work.

Call a demo line and ask to book an appointment — that's a calendar Skill answering. Then build your own agent in the studio.

Free credits included. No credit card required.

LiveCall our demo agent:+1 (720) 572-1333

You're calling a real Flowyte agent. Standard rates apply.