Customer storyAidin logo

Post-acute providers get referral and settings answers in chat, and a HubSpot ticket when they need a person

Aidin runs eesel as the support chat for the providers on its referral network. It answers from the support team's own documents only, and when a question is outside them it opens a HubSpot ticket for the team instead of guessing.

Industry
Healthcare software, patient referrals
Based in
United States
With eesel since
April 2026
Working with
Brian Larsen
150provider chats answered in a month8 Aug to 8 Sep 2026
74HubSpot tickets opened for the teamabout one chat in two ends with a person picking it up
220knowledge searchesbefore answering, every time
500documents it answers fromHubSpot help content, myaidin.com and the team's own files
myaidin.com
Aidin website
How it runs

What happens when a customer writes to Aidin

  1. 1
    A provider opens the chat

    Post-acute providers ask about referrals, insurances and more.

  2. 2
    It classifies the question

    Sorted into referrals, provider settings or account settings.

  3. 3
    It answers from the team's documents only

    Short, plain steps from attached files, or it says it does not know.

  4. 4
    Anything else becomes a HubSpot ticket

    Billing, passwords and gaps go to the team, and the provider is told.

Connected integrations

  • HubSpot
  • wWebsite

Agents at work

  • Aidin Support149 runs in 30 days
  • Userpilot Form Submission Test15 runs in 30 days
  • Account Bot1 runs in 30 days

The company

Aidin makes referral management software for hospitals and the post-acute providers they discharge patients to. Hospitals send referrals through it, providers receive and respond to them, and both sides see where each transition stands. The site says it is used by hundreds of hospitals across the United States and connects more than 21,000 post-acute providers, with over two million referrals a year. Aidin was acquired by LeanTaaS in 2026.

Visit Aidin at myaidin.com

The problem

Providers on the network are clinical and admissions staff, not software people, and the questions are practical. I got a notification but cannot open the referral. We stopped receiving referrals. How do I add a colleague to our account. What does this badge mean. The support team had good written answers for most of these, but the providers were reaching them through a form and waiting.

The team also had a firm requirement: no invented steps, no guesses about what support would do next. A wrong answer about referral routing costs a provider a patient.

How it runs

Aidin set up eesel in April 2026 and spent the spring iterating: first a set of small single-topic bots for referrals, settings and accounts, then one agent, Aidin Support, that covers all three and went live in July. It reads about 300 HubSpot help articles and tickets, about 110 pages of myaidin.com and about 90 files the support team wrote for it.

  • Three domains, one agent. Referrals (finding, receiving, opening and responding to them), provider settings (badges, insurance, referral sources, scores) and account settings (creating an account, adding and removing team members, verified admin status).
  • Only the team's documents count. eesel answers from the attached files and nothing else. If the files do not cover it, it says it does not have enough information and flags it for the team.
  • Escalation is a HubSpot ticket. The ticket is formatted like the existing support form so it lands in the same queue the team already works. eesel confirms it has been logged and does not speculate about what happens next.
  • Tone is calm and short. Providers are busy clinical staff, so answers are action-first, with no jargon they did not use themselves.

A month of work

Between 8 August and 8 September 2026 eesel answered about 150 chats on Aidin's site, ran about 220 knowledge searches and opened 74 HubSpot tickets for the team. Roughly half of chats ended with a ticket, the other half closed in chat. Almost all of it happened during the US working day.

What is next

A second agent for HubSpot tickets is set up and not yet live. When a ticket is created in the Hospital Support or Provider Support pipeline, or a customer replies to one, it will draft a reply as an internal note for the team to review. Legal, security and data questions are always left for a person.

A month of work

What eesel did, from its own records

Every count on this page comes from eesel's activity log for Aidin, 8 Aug to 8 Sep 2026. The only estimate is the money and time saved, and the receipt shows how it is worked out.
$800
of people’s time a month, $10,000 a year
21 hours
about 3 working days, every month

$40 is an international benchmark for an hour of support time, not Aidin’s own cost.

Conversations handled, 8 Aug to 8 Sep 2026159
×Minutes a person would spend on one8
=Hours of people’s time21
×Cost of an hour, all in$40
=A month$800
A year$10,000
website chats and other live work
Live work per week, the last 13 weeks
03467Week of 15 Jun: 22Week of 22 Jun: 6722 JunWeek of 29 Jun: 27Week of 6 Jul: 396 JulWeek of 13 Jul: 46Week of 20 Jul: 4520 JulWeek of 27 Jul: 30Week of 3 Aug: 283 AugWeek of 10 Aug: 34Week of 17 Aug: 3917 AugWeek of 24 Aug: 35Week of 31 Aug: 4731 AugWeek of 7 Sept: 1
Show as a table
Week ofRuns
15 Jun22
22 Jun67
29 Jun27
6 Jul39
13 Jul46
20 Jul45
27 Jul30
3 Aug28
10 Aug34
17 Aug39
24 Aug35
31 Aug47
7 Sept1
When the work arrives
Hour of day, UTC. 9% of it lands between 10pm and 7am, when nobody is at a desk.
00:00 UTC: 500:0001:00 UTC: 002:00 UTC: 003:00 UTC: 004:00 UTC: 105:00 UTC: 106:00 UTC: 106:0007:00 UTC: 008:00 UTC: 009:00 UTC: 010:00 UTC: 011:00 UTC: 112:00 UTC: 412:0013:00 UTC: 1614:00 UTC: 1115:00 UTC: 1416:00 UTC: 1417:00 UTC: 2218:00 UTC: 2418:0019:00 UTC: 1020:00 UTC: 1821:00 UTC: 1122:00 UTC: 523:00 UTC: 1
Show as a table
Hour (UTC)Runs
00:005
01:000
02:000
03:000
04:001
05:001
06:001
07:000
08:000
09:000
10:000
11:001
12:004
13:0016
14:0011
15:0014
16:0014
17:0022
18:0024
19:0010
20:0018
21:0011
22:005
23:001
What it did
Actions taken in the customer's tools, last 30 days
Knowledge searchesKnowledge searches: 223223Tickets created for the teamTickets created for the team: 7474Internal notesInternal notes: 22
Show as a table
ActionCount
Knowledge searches223
Tickets created for the team74
Internal notes2
Where the work comes from
Share of live runs by channel, last 30 days
website chats: 152 (96%)inbound events: 5 (3%)email threads: 2 (1%)
Show as a table
  • website chats 96%
  • inbound events 3%
  • email threads 1%
ChannelRuns
website chats152
inbound events5
email threads2

Hire an eesel teammate for your support

Connect your helpdesk, let it learn from your past tickets, and start with drafts before it replies on its own.

Start free