I've had a clone of myself on the internet for a year plus. Not a metaphor. An actual AI version of me, living at studio.delphi.ai/georgebthomas, answering HubSpot questions in my voice, taking phone calls in my voice, coaching humans through the Superhuman Framework like I would on a Tuesday afternoon.
A year of conversations I didn't have to sit through. A year of help I didn't have to personally deliver.
Today I killed it. Or, more honestly, I moved it.
The Delphi clone still exists for now, but not for long, because Digital George now lives inside HubSpot Customer Agent. Same brain, same voice, different house.
About two hours of config work to rebuild it. And it's already doing things the Delphi version couldn't.
This article is the receipts. Why I moved, how I rebuilt it step by step, what got better, what got worse, and what I'd tell you if you're staring at the same decision.
The Three Reasons I Moved
I wasn't unhappy with Delphi. The clone was a workhorse. I moved for three reasons, and they stack.
1. The Math Finally Worked
HubSpot Customer Agent pricing landed in a zone where the cost-per-conversation story changed. I'm not going to throw numbers in your face because your portal, your volume, and your HubSpot rep are going to shape the real math for you. What I'll tell you is this: the spreadsheet that said "stay on Delphi" last year said "move to HubSpot" this month. If you've been waiting for the economics to shift, pull them again.
2. The Brain Belongs Where the Business Lives
This is the one that matters most. My Delphi clone was an island.
It couldn't see my contacts. It couldn't read a lifecycle stage. It couldn't know whether the human typing was a $48K partner or a brand-new subscriber who just downloaded a PDF. Every conversation started from zero because the clone had no idea who it was talking to.
Meanwhile, every piece of content I've written, every deal I've closed, every email I've sent, every contact I've ever enriched already lives in HubSpot. Putting the clone anywhere else was like hiring a brilliant assistant and asking them to work in a room with no windows and no phone.
Brain, content, and CRM belong in one place. That's the whole bet.
3. Vibe-Code Freedom (And the Actions Kicker)
A year of Delphi updates kept reshaping my team's workflow. Every new capability I added meant rewiring how I handed work off. That's backwards. The tool should wrap the content strategy, not the other way around.
Inside HubSpot, I own the full build surface. Custom Actions can hit any endpoint I spin up on Vercel. That means the agent doesn't just answer questions, it can actually do things: book a call, pull the latest article on a topic, email a resource, log the whole conversation to the contact timeline.
Delphi was a smart chat box. Customer Agent is a smart teammate. That's the upgrade.
What the Delphi Clone Actually Did (Baseline)
Before I walk through the rebuild, here's the honest baseline so you know what I was moving from.
- Channels: Text chat on the Delphi Studio page. Voice and phone calls. Humans could literally call Digital George and get coached.
- Primary jobs: HubSpot how-to, strategy coaching, Superhuman Framework routing, "what would George say about this" decisions.
- Voice settings: 8,000+ characters of free-form prose. A Purpose field. A Speaking Style field. Twelve custom instructions (of a possible 20), including the rule that says "Never use em dashes or en dashes."
- Creativity knob: Adaptive. Not Strict, not Creative. Middle of the road.
- Response length: Concise.
- Citations: Off.
- Production time: One full year.
The clone did what it was built for. I'm not bashing Delphi. I'm just telling you where the ceiling was.
The Migration Walk: Exactly What I Did Today
Here's the order I moved in. If you're migrating your own clone, this sequence kept me out of the weeds.
Step 1: Brand Voice First
Before I touched the agent, I opened Marketing → Brand Identity → Brand Voice (Beta) and filled in the Personality, Tone of Voice, Terms to Avoid, Preferred Phrases, Replacement Suggestions, and Uniqueness fields. This is the upstream setting that every HubSpot AI product reads. Fill it once, it pays off everywhere.
The "Terms to Avoid" field earned its keep immediately. I dropped in "users," "customers," "em dashes," "en dashes," "thrive," "leverage," and a short list of other words I don't want in my voice. "Preferred Phrases" got "humans," "flourish," and the signature Sidekick lines.
Step 2: Define → Identity
Service → Customer Agent → Define → Identity. Avatar uploaded, agent name set, Personality dropdown set to "Use my brand voice." Language left open so the agent detects from the first message.
Delphi gave me 5,000 characters of Speaking Style prose. HubSpot doesn't have that field. The Brand Voice setting in Step 1 is where that fidelity lives now. That's not a downgrade, it's a relocation.
Step 3: Define → Permissions (The 10-Property Budget)
This is where I hit my first real gotcha. Customer Agent can read and write up to 10 contact properties, and it only works on contacts. No companies, no deals, no tickets, no custom objects.
I picked my ten carefully. First name, last name, email, lifecycle stage, lead status, last persona match, partnership tier, last content downloaded, source, and one custom property I use for routing.
The gotcha: lifecyclestage was locked from agent access in my portal. I swapped in hs_analytics_source instead. If you hit the same wall, don't waste half an hour troubleshooting, just sub a different field and keep moving.
Step 4: Train → Knowledge
This is the corpus. Four layers:
- HubSpot Knowledge Base articles (auto re-synced on edit, which is the fastest refresh path in the whole system).
- A domain crawl of sidekickstrategies.com, capped at 5,000 URLs. Weekly refresh.
- File uploads for frameworks and documents that aren't on the public site.
- Short Answers, which is the secret weapon. Manual Q&A pairs where I can guarantee a specific answer in my exact voice. I'm using these as the George-voice override layer for the top 30 FAQs.
If you're coming from Delphi and you want voice fidelity, Short Answers is where you win it back.
Step 5: Train → Guidelines (Beta)
Five sections. Each one mapped from a piece of the old Delphi settings:
- Tone: my voice rules. Contractions, "humans," no em dashes, coach mentality, warm-direct.
- Response style: short paragraphs, concrete examples, always offer a next step.
- Scripted responses: my opener ("Hey there, I'm George, the HubSpot Helper...") and my standard "book a strategy call" close.
- Guardrails: never reference SSOL. Never give legal, tax, or medical advice. Don't commit to pricing without handoff to a human. Don't pretend to be human, the agent IS the Sidekick AI.
- Custom: my story-first bias, "would humans actually use this" filter, HubSpot-first recommendation posture.
Guidelines take a Draft → Test → Publish workflow, which means I can stage changes in preview mode without burning credits.
Step 6: Train → Actions
I deferred Actions to v2. This is where the Vercel endpoints come in (book a call, pull the latest article, send a resource), and I want to ship those on a clean runway, not jam them in on day one.
Step 7: Train → Human Handoff
Ten custom triggers. Keyword-based. Phrases like "talk to George," "cancel," "refund," "partnership tier," and a handful of edge cases. Each one opens a ticket in Help Desk routed to me.
Handoff is the safety net. If I do nothing else right, this means no human ever hits a dead end.
Step 8: Deploy → Channel Settings
- Chat: email capture after the first answer. Two-day inactivity timeout.
- Email: team signature on, reply-to-sender-only, ignore list for a couple of internal domains, five-day inactivity timeout.
- Voice: UNVERIFIED. My portal shows a Voice tab. HubSpot's public docs don't confirm it's GA, don't publish phone-number provisioning details, don't publish per-minute credit burn, don't confirm languages. I emailed my rep today. Until I hear back, I'm treating voice parity with Delphi as an open question.
If you're reading this and a HubSpot rep has given you the voice answer in writing, I want to hear from you.
Step 9: Preview Test (Zero Credits Burned)
Before I flipped the switch, I ran ten real prompts through preview mode. I scored each one against my voice rules: contractions, "humans" not users, no em dashes, handoff triggers firing when they should, pricing deflection working, the whole checklist.
Nine out of ten landed. One response slipped an em dash in. I tightened the Tone guideline, re-ran, clean.
Step 10: Deploy Live
Flipped the toggle. The agent is live on chat today. Email next week. Voice after I get the rep's answer.
The Honest Trade-offs
If I tell you this move was all upside, I'm selling you something. Here's what got worse, or at least harder.
- Voice fidelity is split across four homes. Delphi gave me 8,000+ characters of pure prose. HubSpot splits it across Identity Personality, the Brand Voice setting, Guidelines Tone, and Short Answers. Recoverable, but it takes deliberate mapping.
- No Creativity slider. Delphi had Strict, Adaptive, Creative. HubSpot doesn't expose temperature. You describe the posture in prose and trust it.
- No explicit citation on/off toggle. Delphi had a switch. If HubSpot has a portal-level equivalent, I haven't found it in the public docs.
- CRM personalization caps at 10 contact properties. Contacts only. Plan the ten slots carefully.
- Content refresh is weekly for crawled pages. Real-time only for HubSpot KB articles. If I publish an article Monday, the agent learns it next Monday unless I manually refresh.
- Voice channel docs are thin. Biggest open question.
- No delete, only pause. Once you create the agent, it's there forever. Name it like it's permanent.
None of these are dealbreakers. All of them are things I wish I'd known before I started, which is why I'm telling you.
What the Real Win Looks Like
Here's the part I keep coming back to.
The Delphi clone answered questions. That was the whole job.
Customer Agent answers questions AND acts. The Analyze tab already shows me a Knowledge Gaps view, which is a literal list of questions humans asked that the agent couldn't answer. That's not a report. That's a content roadmap. Every gap is an article, a podcast episode, a video I need to make next. My Delphi clone never gave me that.
When the Vercel endpoints come online in v2, the agent will book calls directly into my HubSpot meetings tool, pull the latest pillar article by topic, email resources from my resource library, and log every single conversation to the contact timeline so my team can see what got said.
Delphi was a smart chat box. Customer Agent is a smart teammate with access to the whole company.
That's the gap that made this worth two hours of config work.
What This Means for You
If you're running a Delphi clone, a custom GPT, an Intercom Fin agent, a Drift bot, or any AI layer that lives outside your CRM, the question isn't whether to consolidate. It's when.
The "when" depends on two things:
- Is the pricing math where it needs to be for your volume?
- Is your brain worth more connected to your business data or sitting on an island?
For me, the answer flipped this month. For you, it might flip next quarter. But the direction of travel is obvious.
If you want help thinking through your own agent strategy, book a strategy call. If you want to learn how to build the content layer that feeds an agent like this in the first place, the AI Content System training is the warmest possible on-ramp. You can also poke around the Sidekick blog for more receipts from the trenches, see what the Sidekick services actually cover, read more about George, or contact the team directly.
FAQ: HubSpot Customer Agent vs Delphi.ai
What's the difference between HubSpot Customer Agent and Delphi.ai?
Delphi.ai is a standalone AI clone platform. You train a "Mind" on your content and voice, and humans chat or call it at a delphi.ai URL. HubSpot Customer Agent is a native CRM-connected AI agent. It reads your HubSpot contacts, knowledge base, and website, and deploys on chat, email, and (in some portals) voice. The biggest practical difference is data: Delphi doesn't know who's talking. Customer Agent does.
Can HubSpot Customer Agent take phone calls like Delphi?
My portal shows a Voice tab under Channel Settings, but HubSpot's public docs don't confirm voice is generally available under Customer Agent as of April 2026. I'm waiting on written confirmation from my HubSpot rep. If voice parity matters to your use case, ask your rep directly before committing to a migration.
Do I lose my Delphi training data when I move to HubSpot?
No. Your training corpus lives on your side, not Delphi's. Export your source documents, then re-ingest them into HubSpot Customer Agent as knowledge base articles, file uploads, or a crawl of your public website. Plan on one to two hours of config work for a solo clone rebuild.
How much does HubSpot Customer Agent cost?
Customer Agent is available on Professional and Enterprise tiers across the HubSpot Hubs and consumes HubSpot Credits per conversation. Exact per-conversation pricing isn't published publicly, and your portal's setup, seat allocation, and credit allotment will shape the real number. Get the numbers from your HubSpot rep before you migrate.
What's the biggest limitation of HubSpot Customer Agent?
The CRM access cap. The agent can only read and write 10 contact properties, and only on the contact object. No companies, deals, tickets, or custom objects. If your personalization story depends on deal stage or custom object data, you'll feel this constraint fast.
Can I still use Delphi and HubSpot Customer Agent together?
Yes. They don't conflict. I kept my Delphi Mind paused (not deleted, because Delphi keeps the data) while I ran HubSpot Customer Agent live. If you want to A/B test voice fidelity or hedge during the transition, running both in parallel for a couple of weeks is the safest path.
How long did the migration actually take?
About two hours of config work spread across one afternoon, assuming your Delphi settings are already documented and your HubSpot Brand Voice is set up. If you're starting from scratch (no Brand Voice, no knowledge base articles, no voice documentation), plan on a full day.
Sources and Further Reading
HubSpot Customer Agent Setup Docs
