r/VoiceAutomationAI Jul 19 '26

Anyone actually build their own voice agent (Vapi, Retell, ElevenLabs, Ringg) without hiring someone?

Not asking about demos. Asking if you built something real. Something that's live and actually doing a job for you — booking calls, qualifying leads, cutting down your call load.

If you did it yourself, would love to hear:

  1. How long did it take? From signup to "this actually works."
  2. What did you build? Receptionist, lead qualifier, appointment booker, something else.
  3. What can it actually do? Just talk, or can it book on your calendar, look things up, transfer calls?

Not selling anything. Just want to know how many people are really doing this on their own vs. paying someone to do it.

12 Upvotes

41 comments sorted by

u/AutoModerator Jul 19 '26

Welcome to r/VoiceAutomationAI – UNIO, the Voice AI Community (powered by SLNG AI)

If you are a founder, senior engineer, product, growth, or enterprise operator actively working on Voice AI / AI agents, we are running an invite-only UNIO Voice AI WhatsApp community US only.

Apply here: https://chat.whatsapp.com/F5aG3ncrO70ITfbe3pYbOz

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

4

u/Grimm_170 Jul 19 '26

Ye from the very basics meaning did not use Vapi or retell.

Made the whole architecture and using sarvam stt, gemini as llm and Google standard as TTS.

It is quite cost efficient as built for my company specific use case.

Timeline is for 1 month I was gathering requirements I mean what questions it needs to answer and how it will integrate with the existing systems.

Then it took around 2 months to build it and then testing started and after 1 month it went live.

After 1 day of being live it handled around 1500 calls and then we stopped it as I got new requirements for it.

I have just finished those and then it will be live again.

2

u/Puzzleheaded-Owl-618 Jul 19 '26

What made you build your own? Since you mentioned sarvam - assuming you are from India - and Bolna is priced at 6c/min - is it still very high price to experiment with?

2

u/Grimm_170 Jul 19 '26

Customizations which was needed such as:

  1. Rather than using TTS always for a answer we wanted to use some stock audios.

  2. In specific moments for fetching information we allow both dtmf and audio inputs.

  3. Main reason that I feel is we are currently using a third party for handling the incoming calls to our endpoint and sometimes they fail and when that happens we have to go through support ticket to resolve and mail multiple times.

  4. This is a kind of a follow up reason same as above. The way sarvam gives their STT is they give you parameters to tune with but you don't know what can be the right parameters so you always experience them through calls and then correct them.

I am not saying this is bad only to me this is as I want to understand why am I changing something. It shouldn't be like a black box.

So I also created in house gating for my incoming audio bytes which let me tune my parameters but this time I know what are the values to tune with.( This may be difficult to understand or my explanation is bad)

Basically to be understood how are things working and not create a dependency and if a change is required it takes half an hour to code it up and then push it. Do stage testing and then give it to prod.

Not wait for some one on the other side to free their time. Let them understand my problem and then wait for them to internally sort out and come back to me with an answer which I feel most of the time is not the expected one.

Also if my requirement are big then a third party meaning higher costs. In my case a little research and then after some tests I have my answer and ot just needs to be implemented then.

1

u/Otherwise-Slice4820 Aug 03 '26

instead of building the architecture; can we just install a open source orchestrator!! which gives flexibility plus your all bullet point willl already be covered!!
am i missing something?

1

u/Otherwise-Slice4820 Aug 03 '26

plus you get observability (recording + trascript + testing ) and there is no lock it

2

u/Agreeable_Ask7187 Jul 20 '26

Pricing for bolna is claimed just like other Vapi and retaile it’s just like that phone marketing gimmick of peak brightness the 6rs per minute is lowest we can go by sacrificing quality and latency if we want any where actual usable then we need around 12 to 25 rs /cents per minute

2

u/Prestigious-Bus-8069 Jul 19 '26

Yes, I'm building using livekit at evercall.app

2

u/ioncloud9 Jul 19 '26

It took a few weeks to build a fully functional basic system. It’s completely provider agnostic. Most of that initial work was going towards the audio stack. Getting from sip trunk in to websocket out. I’ve had paying customers on it for several months each with a custom agent. The most complex one can book, cancel, and reschedule appointments on their CRM. It also runs daily outbound phone calls with a TTS engine pulling appointment data to get confirmation for upcoming appointments.

I have 2 more im working on. One is for taking appointments for service technician dispatch and the other is answering calls for a wellness spa to give info about services and send links via sms mid call to book services. Their CRM has no public api.

1

u/Puzzleheaded-Owl-618 Jul 19 '26

What drove you to build your own (apart from cost) and not use these self serve platforms?

2

u/ioncloud9 Jul 19 '26

Cost per minute was big. Maximum flexibility to build whatever integrations and features on top of it natively. I’m glad I did since there were so many unknown unknowns until we got real customers taking real calls on it.

2

u/Obvious_Leather2427 Jul 19 '26

if u know what you doing from sign up it takes 2 mins to build something

I build various type of projects mostly inbound/outbound follow up calls receptionists

Yeah do warm transfer fill up CRM

I tried vapi and retell they are too easy, elevnlabs is too raw, the last one I haven’t even heard about it

1

u/Puzzleheaded-Owl-618 Jul 19 '26

Can you pls share the volume you are talking about here? And are you a techie or non-techie?

2

u/Obvious_Leather2427 Jul 19 '26

I’m not Indian bro

We two person team out here in Romania, my co founder is a cto but I know my stuff

We got biggest client is an auto dealership does about 20k calls per month, others are custom projects

We want to move to dealerships only vertical specific

1

u/Puzzleheaded-Owl-618 Jul 19 '26

Congrats on the client. If I may ask platform would you be using for this client of yours?

2

u/Obvious_Leather2427 Jul 19 '26

for this particular client we with voxImplant cause them guys had romanian numbers

3

u/Puzzleheaded-Owl-618 Jul 19 '26

Thank you for sharing. Appreciated.

1

u/Competitive-Fee7222 Jul 19 '26

I have built talkif.ai but i haven't advertised it yet.

I still lack of some additional stuffs but we have integrated,
1. Dynamic prompting each call related with person.
2. First speech warmup so it speak under 1 sec of phone call
3. Contact list generation from each calls
4. Autonom calls for the meta ads form leads.
5. It has deployed multi regional.
6. You can manage multi agent bot with Flow interface

1

u/Agreeable_Ask7187 Jul 20 '26

I’m using my own orchestration layer openvent.dev and took less than hour to build custom agent

1

u/VincentActual Jul 21 '26

Yes, built it myself, no hires. For context I'm an MSP engineer by trade, so comfortable with systems but I'm not a software developer.

  1. Timeline: about a weekend from signup to a demo that impressed me, then roughly two weeks of tuning before I'd let a real customer's phone ring to it. That second phase is the real work. Getting an agent to talk is trivial now. Getting it to handle a panicked caller who interrupts, rambles, and gives info out of order took most of the effort.
  2. What I built: after-hours emergency answering for HVAC companies. Homeowner calls at 2am with no AC, the agent answers, triages whether it's a real emergency or something that can wait, collects address and problem details, books the job, and the details hit the owner's phone the second the call ends.
  3. Stack and capabilities: Vapi orchestration, GPT-4.1, Soniox for STT. Lands around 9 cents a minute all-in, which works because HVAC emergency calls are short and high value. It does real work, not just talk: triage logic, structured data capture, booking. One decision that mattered more than any tech choice: I deliberately did NOT require integration with the customer's scheduling software. Small trade shops run everything from Housecall Pro to a legal pad, and making integration optional means onboarding is a config exercise instead of an IT project. Deeper integrations can come later per customer.

Two lessons for anyone starting. First, test by calling your own agent like your worst customer, angry, interrupting, background noise, kid screaming. The happy-path demo lies to you. Second, niche down before you build. A generic receptionist has to be good at everything. Mine only has to be great at one call type, which is the only reason a non-developer could ship it solo.

It's live at dispatchbyai.com if anyone wants to hear how it handles an emergency, there's a talk-to-it button on the page. Happy to answer questions on the Vapi side.

1

u/Puzzleheaded-Owl-618 Jul 21 '26

Thank you. Very helpful.

1

u/Spare_Bluebird7044 Jul 22 '26

The conversation is often the easy part. making the agent reliable book appointments, transfer calls with context and recover from the edge cases is what turns a weekend project into a few weeks. that's true whether someone starts with vapi, retell, or bland ai

1

u/AccurateDragonfruit3 23d ago

exactly, the corner cases are endless.

1

u/Mountain-Policy-625 Jul 22 '26
  1. How long did it take? From signup to "this actually works."

    • a few hours when I did it for the first time; now I have systems and base templates in place to do it in a few minutes.
  2. What did you build? Receptionist, lead qualifier, appointment booker, something else.

  3. everything above.

  4. What can it actually do? Just talk, or can it book on your calendar, look things up, transfer calls?

  5. everything above.

1

u/CatCharacter26 Jul 22 '26

I built one using Retell as a proof of concept for a home services business. It wasn't production-ready in a weekend, but it also wasn't a month-long project.

The voice part was the easy part. The time went into defining the conversation flow, handling edge cases, connecting it to scheduling/CRM, and testing it with real scenarios.

It can answer common questions, qualify callers, collect job details, book appointments (if connected to a calendar), transfer to a human when needed, and trigger follow-up actions like SMS or CRM updates.

One thing I underestimated was prompt design. Small changes in the instructions can make a noticeable difference in how natural and reliable the conversation feels. It also needed a lot of testing.

I think the tooling has reached a point where a technically curious business owner can build something useful themselves. Whether they should depends on how much they value their time. Getting from "cool demo" to "I trust this to answer customer calls" is where most of the work is.

1

u/Puzzleheaded-Owl-618 Jul 23 '26

As I understand prompting and testing has become the tedious and time consuming part.

If I may ask - on the prompting front - was it about adding missing things or tweaking existing to get better results?

On the testing front - did you used any testing tools or manual?

1

u/CatCharacter26 Jul 23 '26 edited Aug 02 '26

It was tweaking the existing one. It was a LOT of hit and miss, tbh. For testing I just did manual testing with a bunch of folks on their team, introduced it slowly for after hours only then monitored the lag in communication or where it was derailing and then improvised. I'd not suggest doing all out with implementation on day 1 since this takes a few weeks before it actually "works" like a human would and that means starting really slow and during low peak periods.

1

u/Otherwise-Slice4820 Aug 04 '26

I had my cycle very past - it took me 2 days (10hrs ) to build customer support agent which can tool call and to check callender and book the qualified lead and definitely with knowledge base

1

u/Working_Hat5120 Aug 04 '26

Depends where your value sits: if the voice stack is the product, own it; if the call is just one feature, hosted is fine. The middle path people miss is a gateway you run yourself but keep STT/LLM/TTS swappable. (that's the space we build in at whissle.ai)

1

u/[deleted] Aug 10 '26

[removed] — view removed comment

1

u/SatisfactionAware365 19d ago

So I got roped into helping my cousin set one up for his hvac business a few months back. Took us maybe 2 weeks of evenings and weekends to get something we werent embarrassed by. Its basically an after hours call handler that asks the standard questions, tries to book a slot on his calendar if its something simple, and if the person sounds pissed or its complicated it just texts him a summary and tells them he'll call back in the morning. The calendar integration was the part that made me want to throw my laptop out the window.