> For the complete documentation index, see [llms.txt](https://docs.raiaai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raiaai.com/use-cases/case-study-nexthome.md).

# Case Study: NextHome

**NextHome arms its fast-growing franchise network with an AI “Agentic Workforce” powered by raia**

***

**Snapshot**

| **Metric**                                | **Before raia**                    | **After raia (AI Agents)**                                      |
| ----------------------------------------- | ---------------------------------- | --------------------------------------------------------------- |
| Agent support response time (after hours) | E-mail queue, **≈ 4 h** avg.       | **< 2 min** via chat / SMS — 24 / 7                             |
| Lead-response coverage                    | ≈ 50 % of online inquiries touched | **100 %** contacted & qualified by AI                           |
| Demos / appointments booked per month     | 120                                | **310** (+158 %)                                                |
| Recruiting outreach to loan officers      | 1 000 manual emails / mo.          | **6 000** personalised messages / mo.; 3× more intro calls      |
| Event RSVP & FAQ handling                 | One-way email blasts               | Conversational AI drives **78 %** RSVP & answers FAQs instantly |
| Equivalent human capacity added           | —                                  | **≈ 6 FTEs** (3 support + 2 SDR + 1 recruiter)                  |

> “If you’re not deploying AI today, you’ll be years behind your competition. Raia lets us spin up highly custom agents fast—an indispensable partner on our road to AI.”\
> **Keith Robinson, Co-CEO, NextHome**

***

#### 1 | Company & Challenge

NextHome is one of the fastest-growing real-estate franchises in the U.S., with **600 + offices and 6 000 + members** and an ambition to double in size within four years. Growth pressures showed up in three areas:

1. **Agent Support** — Thousands of associates needed instant answers on marketing tools, compliance and tech setup.
2. **Recruiting** — Franchise owners wanted to court loan officers and new agents at national scale without losing the personal touch.
3. **Event & Lead Engagement** — Webinars, open houses and online buyer leads demanded round-the-clock conversation.

***

#### 2 | Why NextHome chose raia

* **Omnichannel from day one** — chat, SMS, email and voice funnel into a single conversation timeline.
* **Rapid knowledge ingestion** — 12 000 + pages of playbooks, FAQs and call transcripts vectorized in hours for precise retrieval.
* **CoPilot human-feedback loop** — staff rated draft answers during a 60-day shadow phase, lifting accuracy above 95 % before go-live.
* **No-code CRM & calendar hooks** — agents push qualified leads to kvCORE, book meetings in Outlook/Calendly, and sync RSVPs with Eventbrite.

***

#### 3 | Solution Design

| **AI Agent**            | **Primary Role**                                                                      | **Key Integrations** |
| ----------------------- | ------------------------------------------------------------------------------------- | -------------------- |
| Agent Support Concierge | 24 / 7 answers on marketing suite, MLS feeds, compliance; escalates edge cases.       | Vector KB, Zendesk   |
| Sales-Qual Agent        | Engages buyer/seller leads, asks discovery, books appointments with member agents.    | kvCORE API, Calendly |
| Recruiter Agent         | Sends personalised outreach to loan officers & agents, handles Q\&A, schedules calls. | HubSpot, email / SMS |
| Event & Conference Bot  | Manages RSVPs, answers agenda/venue questions, sends reminders.                       | Eventbrite, SMS      |

***

#### 4 | Implementation Timeline

1. **Weeks 1–2** — Upload franchise manuals & transcripts to Launch Pad.
2. **Weeks 3–6** — Shadow mode in CoPilot across 10 pilot offices; tone & routing refined.
3. **Week 8** — National launch of Support & Sales agents.
4. **Month 4** — Recruiter and Event bots deployed; Spanish language pack added.

***

#### 5 | Results (first 5 months)

* **≈ 25 000 conversations / month** handled; 68 % resolved or scheduled by AI with no human touch.
* **Lead demo-set rate +158 %** (120 → 310 / month).
* **Recruiting reply rate** tripled (6 % → 18 %).
* **Agent support CSAT** rose from 4.0 → **4.7**.
* AI workload equals **≈ 6 full-time employees**, saving ≈ US $500 k / year.

***

#### 6 | Key Takeaways

1. **Solve agents’ pain first** — instant support wins field buy-in.
2. **Clone agents, don’t rebuild** — new offices receive a tailored concierge in under an hour.
3. **Keep the human option** — users can escalate to a live person any time, preserving relationship-based service.

***

NextHome’s experience shows that **raia’s Agentic Workforce turns AI into a growth engine—supporting agents, amplifying recruiting and converting leads around the clock—without expanding headcount.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.raiaai.com/use-cases/case-study-nexthome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
