Building a Customer Service Agent with AgentKit 1.0: A Florida Case Study

A Miami-based property management company managing 4,200 units across South Florida deployed an AgentKit 1.0 customer service agent in late March 2026. By mid-April it was handling 73% of inbound tickets without human escalation. Here is the architecture.

The Problem Space

Florida property management is operationally brutal. Hurricane season, snowbird tenants, frequent maintenance escalations, and a multilingual tenant base (English, Spanish, Haitian Creole, Portuguese). The company's call center was at capacity with 14 agents handling roughly 800 tickets per day.

The Architecture

graph TB
  A[Tenant Channel: Phone, SMS, Web] --> B[Voice/Chat Agent]
  B --> C[AgentKit Triage Node]
  C -->|Maintenance| D[Maintenance Sub-Agent]
  C -->|Billing| E[Billing Sub-Agent]
  C -->|Lease| F[Lease Sub-Agent]
  C -->|Emergency| G[Human Escalation]
  D --> H[Vendor Dispatch via Operator]
  E --> I[AppFolio Lookup via Tool]
  F --> J[Document Retrieval]

The triage node is a GPT-5.2 call with a structured output schema. It classifies the ticket and routes to a specialist sub-agent. Each sub-agent has its own context window and its own tool set, scoped to the specific domain.

Tool Integrations

The agent integrates with:

• AppFolio (the property management system) via REST API
• A vendor dispatch system via Operator 2.0 (for vendors without APIs)
• Twilio for SMS and voice
• A document store with all leases and addenda
• A knowledge base of building-specific quirks (which units have which appliances, etc.)

Costs

Monthly run-rate at 800 tickets/day:

• AgentKit platform: ~$1,800
• GPT-5.2 tokens: ~$5,400
• Voice provider (CallSphere): ~$2,200
• Operator 2.0 for vendor dispatch: ~$900
• Total: ~$10,300/month

Replaced cost: roughly 8 of the 14 call center agents at fully-loaded $4,200/month each = $33,600/month. Net savings: ~$23,000/month.

What CallSphere Brings

The voice agent layer is CallSphere. The customer chose us because of native multilingual support (English, Spanish, Haitian Creole, Portuguese all in one config) and our tight AgentKit integration that handles tool calls without round-tripping through the voice provider's intermediary layer. The deployment took 11 days from contract to production.

What Worked

• Aggressive use of guardrails to keep the agent from making promises (escalation thresholds, refund limits, etc.)
• Per-building knowledge base gave specific answers instead of generic ones
• Human escalation always available, with full context handoff
• Tenant satisfaction scores rose 18% in the first 30 days

What Did Not Work Initially

• The agent over-escalated maintenance issues for the first two weeks. Tuning the triage prompt with 50 historical tickets fixed it.
• Spanish handling was weaker than English on technical building terminology. A custom glossary fixed this.
• After-hours emergency triage required a sharper guardrail to ensure true emergencies always reached a human within 90 seconds.

Frequently Asked Questions

How long was the build? 11 days from kickoff to production for the core flow. Continuous tuning since.

What about complex tenant disputes? Always human-handled. The agent gathers facts and hands off with a structured summary.

Is tenant data secure? Yes, with OpenAI's enterprise BAA, zero-data-retention configuration, and tenant-level access controls.

Could this work for residential rather than property management? Yes, the architecture generalizes to any high-volume customer service workload.

Sources

• https://openai.com/blog/agentkit-1-0
• https://www.theverge.com/2026/4/16/agentkit-customer-service-case-study
• https://techcrunch.com/2026/04/16/property-management-ai-florida
• https://www.bloomberg.com/news/articles/2026-04-16/proptech-ai-adoption

## How this plays out in production One layer below what *Building a Customer Service Agent with AgentKit 1.0: A Florida Case Study* covers, the practical question every team hits is multi-turn handoffs between specialist agents without losing slot state, sentiment, or escalation context. Treat this as a voice-first system from the first prompt: the agent's persona, its tool surface, and its escalation rules all flow from that single decision. Teams that ship fast tend to instrument the loop end-to-end before they tune any single component, because the bottleneck is rarely where intuition puts it. ## Voice agent architecture, end to end A production-grade voice stack at CallSphere stitches Twilio Programmable Voice (PSTN ingress, TwiML, bidirectional Media Streams) to a realtime reasoning layer — typically OpenAI Realtime or ElevenLabs Conversational AI — with sub-second response as a hard SLO. Anything north of one second of perceived silence and callers either repeat themselves or hang up; that single number drives the whole architecture. Server-side VAD with proper barge-in support is non-negotiable, otherwise the agent talks over the caller and the conversation collapses. Streaming TTS with phoneme-aligned interruption keeps the cadence natural even when the user changes their mind mid-sentence. Post-call, every transcript is run through a structured pipeline: sentiment, intent classification, lead score, escalation flag, and a normalized slot extraction (name, callback number, reason, urgency). For healthcare workloads, the BAA-covered storage path, audit logs, encryption-at-rest, and PHI-safe transcript redaction are wired in from day one, not bolted on at compliance review. The end state is a system where every call produces a row of structured data, not just a recording. ## FAQ **What is the fastest path to a voice agent the way *Building a Customer Service Agent with AgentKit 1.0: A Florida Case Study* describes?** Treat the architecture in this post as a starting point and instrument it before you tune it. The metrics that matter most early on are end-to-end latency (target < 1s for voice, < 3s for chat), barge-in correctness, tool-call success rate, and post-conversation lead score distribution. Optimize whatever the data flags as the bottleneck, not whatever feels slowest in your head. **What are the gotchas around voice agent deployments at scale?** The two failure modes that bite hardest are silent context loss across multi-turn handoffs and tool calls that succeed in dev but get rate-limited in production. Both are solvable with a proper agent backplane that pins state to a session ID, retries with backoff, and writes every tool invocation to an audit log you can replay. **What does the CallSphere outbound sales calling product do that a regular dialer does not?** It uses the ElevenLabs "Sarah" voice, runs up to 5 concurrent outbound calls per operator, and ships with a browser-based dialer that transfers warm calls back to a human in one click. Dispositions, transcripts, and lead scores write back to the CRM automatically. ## See it live Book a 30-minute working session at [calendly.com/sagar-callsphere/new-meeting](https://calendly.com/sagar-callsphere/new-meeting) and bring a real call flow — we will walk it through the live outbound sales dialer at [sales.callsphere.tech](https://sales.callsphere.tech) and show you exactly where the production wiring sits.