explaingit

pawel-cell/vapi-phone-agent-use-cases

12Audience · pm founderComplexity · 1/5Setup · easy

TLDR

A swipe file of 80 ready-made ideas for building AI-powered phone agents with Vapi, 40 inbound scenarios and 40 outbound scenarios to pick from and adapt.

Mindmap

mindmap
  root((vapi-phone-agent-use-cases))
    Inbound ideas
      Appointment scheduling
      Call routing
      Lead qualification
      Customer support
    Outbound ideas
      Follow-up calls
      Renewal reminders
      Survey calls
      Re-engagement
    How to use
      Pick one use case
      Connect one system
      Ship minimal first
    Audience
      Founders
      PMs
      Builders
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Pick an inbound idea like appointment scheduling and build an AI receptionist for a clinic or business in a day.

USE CASE 2

Use the outbound list to add automated follow-up calls to leads who showed interest but did not convert.

USE CASE 3

Use the swipe file to pitch an AI phone agent concept to a client with a concrete list of starting points.

Tech stack

VapiMarkdown

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

This repository is a reference collection of 80 ideas for building AI-powered phone agents using a platform called Vapi, which handles the telephony and voice side of automated phone calls. The collection is split into two lists of 40 ideas each: one for inbound scenarios, where the AI answers incoming calls, and one for outbound scenarios, where the AI places calls to people. The inbound list covers situations like reception and call routing, intake forms, scheduling appointments, customer support, lead qualification, and triage, where a caller needs to be directed to the right place or person. The outbound list covers situations like following up with people who showed interest but did not convert, sending reminders, recovering lost customers, conducting surveys, handling renewals, and reaching out quickly after a new inquiry comes in. The README frames these as swipe files, meaning ready-made starting points you can pick from and adapt rather than build from scratch. The suggested approach is to choose a single use case, define clearly what the caller is trying to do, connect the phone agent to the relevant system (a calendar, a CRM, a support tool), and ship a minimal version first. The README recommends starting with one caller type, one business process, one measurable goal, and one clear path to a human if the agent cannot handle the situation. Then expand from there once that first workflow is working reliably. The repository contains no code, only the two markdown documents with the use case lists. It is a planning and idea resource rather than a technical implementation.

Copy-paste prompts

Prompt 1
Using the vapi-phone-agent-use-cases inbound ideas, write a Vapi system prompt for a dental clinic AI receptionist that schedules appointments and routes urgent calls to a human.
Prompt 2
I want to build an outbound Vapi agent that calls leads from a form submission who did not convert. Based on the outbound use cases in this repo, draft the Vapi agent config and a sample call script.
Prompt 3
Help me define a minimal first version of a Vapi phone agent for appointment reminders, following the one-caller-type, one-process, one-goal framework from vapi-phone-agent-use-cases.
Prompt 4
Using the inbound use cases from this repo, write a Vapi system prompt for a hotel front desk agent that handles booking inquiries and escalates complaints to a live person.
Open on GitHub → Explain another repo

← pawel-cell on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.