Connected.
Not wired up.

Campaigns that write back.

• Message a dormant candidate list as one campaign, not as 200 single chats.
• The AI answers follow-up questions, even at 9 pm, in the tone of your house.
• Intro appointments land in the calendar without anyone picking up the phone.
• Every conversation is attached to the candidate in alluvo, not to a private phone.

Recruiting ads straight from the system.

• Start, change and stop campaigns for open jobs directly from alluvo.
• Whoever responds becomes a candidate in the system, instead of an email in the inbox.
• What an application cost sits next to the campaign, not in a second ad account.

If you already work with HubSpot, that stays the way it is.

• Companies, contacts and activities stay in sync between alluvo and your HubSpot CRM.
• Your sales team maintains one record, not two: both sides see the same state.
• Switching on command: if you want to stay with HubSpot, you can. alluvo does not replace it, it mirrors it.

Sign-in, calendar, mailbox: with the account your house already has.

• Sign-in with the Microsoft account: no second password, no second user list.
• The Outlook calendar is connected to alluvo: appointments, cancellations and free times are the same on both sides.
• Your mailbox is handled in alluvo: read, reply, assign, without switching tabs.
• Shared company mailboxes (info@, applications@, dispatch@) run as a case for the whole team, not as a forwarding chain.

The same with Google: sign-in, calendar, mailbox.

• Sign-in with the Google account: whoever leaves the house loses access where it is withdrawn anyway.
• Google Calendar and alluvo keep the same appointment state: you plan in the calendar you already have open.
• Gmail is handled in alluvo: the email is attached to the candidate, the client, the assignment.
• Group mailboxes of the domain land in the shared inbox instead of getting stuck in a private folder.

Ask questions and hand out work where your team already reads.

• “Who is free from Monday?” The answer comes into the channel, not into yet another tool.
• Commands take the same route: capture a demand, suggest candidates, write to clients. You write it in Slack, alluvo does it in the background.
• What happened, alluvo reports back in the same thread, and it is kept as a case in the system, not only as a message.
• Notifications from alluvo land in the team channel instead of one more inbox.

One inbox for the case, not for the person.

• Mailboxes come together in alluvo: emails are attached to the candidate, the client, the assignment.
• Calls are noted on the record, instead of on a slip of paper next to the keyboard.
• Whoever is on vacation no longer blocks a case: the history is there for everyone.

Talk to your dispatch. In plain language.

• Ask who is on the bench from Monday, and which clients could need them right away.
• A voice message after the client appointment: back at the office, the assignment contracts are waiting as drafts.
• Answers come from your data, not from general knowledge. And you see what they rest on.

The same connection, the same access: a different assistant.

• The same tools as in Claude: what one assistant can do, the other can too.
• The same limits: what the person asking is allowed to do counts, not which window is open.
• You decide which assistant may reach which data. And you change that without building anything new.

The connection is in place. Only the assistant is missing.

• MCP is an open standard: anyone who speaks it can connect to alluvo, we do not have to build anything new for it.
• We test every assistant ourselves before it is listed here as usable. That is why it sits here until then.