--- title: "Custom AI Receptionist Setups We've Built (2026)" description: "Real dolfyn builds: after-hours relay calls, department routing, selective calendar booking, IVR takeovers, custom integrations. No two are the same." canonical: https://dolfyn.ai/custom-builds source: dolfyn.ai --- # Custom AI Receptionist Setups We've Built (2026) > Real dolfyn builds: after-hours relay calls, department routing, selective calendar booking, IVR takeovers, custom integrations. No two are the same. Real Builds # Custom Setups We've Built Updated **September 2026**7 min readTrades · Property Management · Multi-Service dolfyn Editorial AI voice agents and call handling for service businesses. The Point **Every business is different. So is every AI receptionist we build.** That is easy to claim and harder to show, so this page shows it: real setups running for real dolfyn clients right now, anonymized, described the way we would describe them to you on a call. Key Takeaways dolfyn builds are custom by default: one agent or a team of them, each with its own job, sounding like one seamless receptionist. Live setups include after-hours relay calls that phone the on-call tech, department routing across leasing and maintenance, selective calendar booking with availability rules, full IVR takeovers, and integrations into Monday.com, Buildium, ServiceTitan, Jobber, and one client's homegrown lead tracker. Plans start at $179/month, scoped before go-live. ## The after-hours build that phones the on-call plumber The client's problem was specific: after-hours techs sleep through text notifications, and a slept-through emergency is a lost job plus an angry customer. The build we shipped answers the emergency call, captures everything, then a second agent dials the on-call plumber directly and reads the situation to them over the phone. Rejected or unanswered? It dials the next tech on the list, and keeps going until a human owns the job. The customer with the burst pipe sees none of it. They just get a fast callback from someone who already knows what is wrong. ## Built around a front desk that already exists A trades company with a real person at the front desk did not need a replacement. They needed everything she cannot catch. Their build is three agents: a general agent as backup, an overflow agent that picks up whenever she is already on a call, and a separate after-hours agent for nights and weekends. All three route the same way she does. Nobody hits voicemail, and nobody lost their job to a robot. ## One number, every department Bigger operations do not have one kind of call, so they do not get one kind of agent. The caller dials one number and describes the problem. An intake agent figures out where it belongs and passes it to the specialist built for that department, leasing, service, billing, installs, with no hold, no menu, and no sign a transfer happened at all. Narrow agents win on accuracy: the leasing agent has leasing questions sharpened into it and nothing else diluting them. ## Two different agents, day and night For one client we run a daytime agent and an after-hours agent that are completely different builds. Different greeting, different questions, different escalation rules. What they share is the routing, so a lead captured at 2pm and a lead captured at 2am land in the same place, formatted the same way. The business reads one pipeline. The callers get an agent built for the hour they called. ## Books some jobs. Deliberately holds others. A multi-service company that handles hot water tanks, plumbing repairs, salt delivery, and filtration wanted booking, but only where booking makes sense. Their agent books hot water tank jobs and salt deliveries straight into the calendar, checking who is available and respecting time windows that change by day of the week. But leaks and repairs never get booked. Job length varies too much, so the agent captures everything and the office calls back to schedule it themselves. The agent knows the difference because we built it knowing the difference. ## Leasing to Monday.com, tenants to Buildium A property management client runs on two systems, so their agent does too. Leasing inquiries get qualified and pushed into Monday.com where the sales pipeline lives. Tenant maintenance calls get logged into Buildium where operations lives. One phone number, one conversation for the caller, two clean systems for the team. No enterprise platform we know of offers that split out of the box, which is exactly why it had to be built. ## Wired into a homegrown lead tracker A roofing company tracks leads in their own custom-built tool. Not ServiceTitan, not a spreadsheet, their own software. We built the integration into it as part of their setup, so every call the agent handles lands in the tracker they already trust. If your software has an API, the integration gets built. That is the standing rule. ## The entire first point of contact For one company, dolfyn is the whole front door. Callers can ask for a specific person by name and get transferred. They can ask for whoever is available. Or the agent simply takes everything down and relays it to the right desk. Smart transfer when a human should pick up, clean capture when a message does the job. The company decided the rules, and the agent runs them. ## Replacing the phone tree entirely dolfyn can also take over a full IVR system, the press-1-for-service phone trees that businesses run on tools like Grasshopper. The menu becomes a conversation. Callers say what they need instead of guessing which number it hides behind, and the routing intelligence underneath stays, now combined with agents that can actually answer questions and book the work. We can replace the whole system or combine agents with what you already run. ## The parts every build gets Some things are standard because they should be. Emergency protocols are built into every agent: a caller who mentions a gas smell is told to leave the building and call the gas utility, a burst pipe caller gets walked to the water shutoff, and the call is flagged urgent before it ends. Addresses get verified against Google Maps in real time during the call, catching misheard street names before a tech drives to the wrong place. And real people review calls every day, tuning each build as real calls surface real edge cases. ## No CRM? We build you one. Some clients come to us with no system at all, and that is fine. We build them one as part of the setup, online or as a structured spreadsheet, so call data has somewhere clean to land from day one. Start simple, upgrade whenever you are ready, and the agent comes along. ## What would yours look like? None of these setups existed before the client that needed them. That is the actual product: not a feature list, but a build. Tell us how your business runs and we will tell you what we would build, plainly, before you pay anything. Plans start at $179 a month, scoped to your call volume before you go live, month to month, with a 2-week free trial on your real calls. ### See how dolfyn handles calls for your business Tell us your name, company, and number. We'll call you to walk through how it works for your specific business. No pitch deck, no pressure. Get a callback Got it. We'll be in touch shortly. ### Related [Integrations: connects to any software with an API](https://dolfyn.ai/integrations)[962 real calls, analyzed](https://dolfyn.ai/call-data)[How dolfyn compares](https://dolfyn.ai/compare)[The story behind dolfyn](https://dolfyn.ai/about) --- *Source: [https://dolfyn.ai/custom-builds](https://dolfyn.ai/custom-builds)* *dolfyn: custom-built AI receptionists for businesses that run on calls* *Starts at $179/month. 2-week free trial. No contracts. [dolfyn.ai](https://dolfyn.ai)*