Bringing your contacts to Aethex

Your CRM is the call list

Connect the CRM your team already works in, grant it to an agent, and the people it calls are the people your CRM says to call, at the moment it dials. No export, no spreadsheet, no list that was accurate last Tuesday.

The spreadsheet in the middle

Every outbound programme without a CRM connected has the same shape. Somebody filters the CRM, exports a file, and hands it to whatever places the calls. It works on the first day.

By the second week the file is a fork in the road. Corrections go into the CRM, because that is where the sales team lives. Calls go out of the file. Four numbers have changed, two people have asked not to be called again, one contact is in there three times, and the thing dialling knows none of it.

An agent makes this sharper rather than softer, because it works a list faster than a person and calls every row without a rep’s instinct that a record looks wrong. The fix is not a cleaner export. It is removing the file from the middle.

What Aethex does with a connected CRM

Aethex supports connections to several of the CRMs businesses actually run on. You connect one from the Integrations page, and it does three things.

It supplies the list. A saved segment or filter in your CRM becomes the list an agent dials. Contacts that enter the segment enter the list; contacts that leave it stop being called.

It supplies the context. The fields you map arrive with the contact, so the agent opens the call knowing the renewal date, the outstanding balance, the branch, the language to speak.

It takes the outcome back. The disposition, the summary and what was agreed return to the CRM record. If they do not, you have not connected two systems — you have made a second version of the truth and given everyone a reason to distrust both.

The four fields that do the work

A CRM holds contacts, the companies they belong to, deals in motion, activity history, and the custom fields that are specific to you. On a call, four of them carry it.

The number. What the agent dials, and what it matches an inbound caller against.

Consent. Whether this person may be called at all, read on every sync in the direction that fails safe. A record whose consent field could not be read is not a record to call.

The reason for the call. The field that makes the first sentence specific rather than generic. It is why a connected CRM beats a name and a number.

The email address. The genuinely hard part of anything done by voice: spelling one aloud is slow and the transcript is rarely exact. But the number the caller is on, the agent already has — matched against the CRM, it produces a verified address the agent only has to read back.

Before any of that dials, numbers are normalized and contacts deduplicated. Aethex already refuses to build a call list out of numbers it cannot ring, because a wrongly-formatted number does not fail loudly; it fails as an unanswered call. A CRM connection is held to the same standard, and the same human sitting in your CRM three times is called once.

Looking and acting: the line that holds

Connecting a CRM stores a credential. It hands it to nothing. A connected CRM with no agent granted access is connected and completely inert — connecting one should not expose your customer database to every agent in the workspace because somebody clicked a button.

Access is granted per agent, at one of two levels. Looking: the agent may match a caller and read the fields you mapped. Acting: it may also write back to the record.

It is a level rather than a checklist of fields, because reading a contact and writing its outcome chain into each other and picking them apart mostly produces combinations that cannot work. And it is enforced by omission rather than refusal: what an agent can reach is settled when the call is assembled, so an agent without write access does not decline to update a record. It has no notion of updating a record to decline, which is a considerably stronger guarantee than a prompt asking it nicely.

What the caller actually hears

Caller: Hello, I’m calling about my policy.

Agent: Of course. This is Kwame Mensah, on the motor policy renewing on the twenty-third?

Caller: That’s me.

Agent: You’re due in sixteen days, and the premium is the same as last year. I can take the renewal now, or send the link to the address ending in mensah at gmail. Which would you prefer?

All of that came out of the CRM in the second before the agent spoke. The caller was matched on the number they rang from, so nobody read out a reference. The premium and the date are what the CRM says now, not what a file said a fortnight ago. When the call ends the outcome goes back onto the record, and the transcript arrives on your webhook as it does for every call.

Four businesses, four setups

A microfinance lender chasing repayments. One arrears segment, granted with write. The balance quoted is this morning’s, every promise-to-pay lands back on the account for whoever calls next, and the list empties itself as people pay.

A clinic confirming appointments. A CRM connection for who the patient is, a calendar connection for when they are due. Matched by number, the agent greets a patient by name and confirms without either side reading out a reference.

A distributor with eight branches. One connection per branch account, each granted to that branch’s agent. Overhead, until the week it is the reason a branch agent could not read another branch’s customer list.

A B2B team qualifying inbound. Two agents, one CRM. The front desk is granted looking only: it recognizes the caller, then routes or transfers. The agent that takes qualified callers is granted write and logs what came of it. One connection, two levels of authority, which is why grants are per agent rather than per connection.

The limits worth knowing before you launch

Clean first, connect second. A connection reproduces your duplicates, dead numbers and unmapped fields faithfully. It is a mirror, not a repair.

Start with one segment. Mapping errors are obvious in the first hundred records and invisible after the first hundred thousand.

Test consent with a record you flagged yourself, rather than inferring that opt-outs are honored because nobody has complained yet.

Disconnecting does not undo anything. Every granted agent loses access immediately, but calls already placed and records already written stay exactly as they are.

Get started

Connect a CRM from the Integrations page, grant one agent, point it at one segment, and place a test call to a record you can open afterwards and check. The rest is the list you were already working, minus the spreadsheet in the middle.

developers.aethexai.com/docs