Does ai-receptionist use paid AI services?

Can use OpenAI. Its settings have keys for this paid API. Its README says whether one is required.

Is ai-receptionist still maintained?

Yes, active. Last change 2 months ago.

Can I trust ai-receptionist?

New, little track record. 2 stars, 2 months old. Look at the code and the owner before running it.

gitmanual

Reading the repo

Opening the box…

How to install ai-receptionist on Linux (jbrazy480/ai-receptionist) · gitmanual

How to install on Linux

jbrazy480/ai-receptionist

Open source AI receptionist starter for local businesses, agencies and GoHighLevel builders. Answers inbound calls with Twilio and OpenAI Realtime, handles FAQs and business hours from YAML, takes messages, transfers calls and books appointments via webhook. Self-hosted Python and FastAPI. Want it done for you? RizzDial.

Python#agency#ai-phone-agent#ai-receptionist#ai-voice-agent

Before you start

Is it free?: YesOpen source (MIT).
Paid AI services?: Can use OpenAIIts settings have keys for this paid API. Its README says whether one is required.
Still maintained?: Yes, activeLast change 2 months ago.
Can I trust it?: New, little track record2 stars, 2 months old. Look at the code and the owner before running it.

Difficulty: Moderate
Time: about 15 min
Stars: ★ 2
Activity: Updated 2 months ago

GitHub didn't answer, so this is the saved copy from 17 h ago

Will it work on Linux?

Yes, it runs on Linux

You'll build it yourself with Python.

Your system

macOS Windows Linux

Start here

Website ↗rizzdial.comThe project's own site.

Heads-upBuilding it yourself? It also needs 7 settings in .env (2 secret).

From the maintainers

Development setup: `CONTRIBUTING.md`

Contributing

Contributions are welcome. This is a starter project meant to stay small and readable.

Getting set up

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements-dev.txt
cp business.example.yaml business.yaml
pytest

Guidelines

Keep the offline demo (python -m receptionist.simulate) working with zero API keys and no network access.
Add tests for any new tool, config field, or bridge event you handle. Tests must run offline (no real Twilio or OpenAI calls).
Follow the existing module layout: business logic in receptionist/, tests in tests/.
Run pytest before opening a pull request.
Keep pull requests focused on one change.

Reporting issues

Open a GitHub issue with steps to reproduce, what you expected, and what happened instead.

Open CONTRIBUTING.md on GitHub ↗

4 steps on Linux

Download setup.sh

Then run bash setup.sh. It stops at the first error and is safe to run again. Servers and tests aren't started; it lists them at the end. Read it first.

Clone the repository

git clone https://github.com/jbrazy480/ai-receptionist.git
cd ai-receptionist

2
Install the required runtimes
Python 3.x (no version pinned)
```
sudo apt install python3 python3-venv  # Debian/Ubuntu
```
3
Configure environment variables
Fill in secrets: OPENAI_API_KEY, TWILIO_AUTH_TOKEN
```
cp .env.example .env
```

Install dependencies

python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
pip install -r requirements-dev.txt

Did you get it running?

No reports for Linux yet.

Still stuck? Get a written guide

GitManual AI Agent reads the 8 key files and writes a step-by-step guide for Linux. Once written, it's saved for everyone.

Parts list

1×Python 3.x (no version pinned)runtime
1×pip package manager

7× settings in .env

OPENAI_API_KEYsecret
TWILIO_ACCOUNT_SID
TWILIO_AUTH_TOKENsecret
VALIDATE_TWILIO_SIGNATURE
BUSINESS_CONFIG_PATH
PORT
LOG_LEVEL

Share this manual

Is this your repo?

Add a badge to your README so newcomers find these steps.

[![Setup manual](https://gitmanual.com/jbrazy480/ai-receptionist/badge.svg)](https://gitmanual.com/jbrazy480/ai-receptionist)

Good to know

Dockerfile available (base image: python:3.11-slim).
Has AGENTS.md — instructions for coding agents. You can open Claude Code (or another agent) in the cloned folder and ask it to do the setup for you.

Details

License: MIT
Open issues: 0
Branch: main

Files we read (8)

.env.example

.github/workflows/ci.yml

CONTRIBUTING.md

Dockerfile

README.md

docker-compose.yml

requirements-dev.txt

requirements.txt

55 files in the repo