Workflow · Database Re-activation

AI voice agents for database re-activation.

A Xebit re-activation agent works through the leads and candidates already sitting in your CRM or ATS: old enquiries, lapsed customers, past applicants. It checks whether they are still interested, refreshes their details and preferences, records consent to stay in touch, and passes anyone ready to move to your team with the conversation attached.

Book a walkthroughHear it live· Coming soon

How the call runs

See how one dormant record becomes a warm candidate again.

A past applicant's location and preferences are refreshed, consent is recorded and a recruiter gets the call back.

Calling…

Agent is reaching a past applicant

Live conversation

Outbound re-activation call

Live
Waiting for the caller to pick up…

Workflow actions

Triggered during the call

Actions appear here as the conversation progresses.
Step by step

How does the call run?

The agent follows your script, your rules and your calling windows. Each step below happens inside one live call.
  1. 01

    Choose the segment

    You pick the dormant records to call by age, source or status. Xebit pulls them through the API or the Zoho and Salesforce connector and runs them as a campaign.

  2. 02

    Pace the campaign

    Dialling plan, retries, pacing and calling windows are set by you, so a large list runs steadily without flooding your team with transfers.

  3. 03

    Reopen the conversation

    The agent reminds the person of their earlier enquiry or application and asks whether their plans have changed.

  4. 04

    Refresh the record

    It updates contact details, current needs, budget or availability, and records whether they want to hear from you again.

  5. 05

    Pass on the warm ones

    People ready to act are booked for a next step or transferred live. Everyone else is tagged so the record reflects where they stand.

Outcome

What does the agent capture, and where does it go?

Captured during the conversation, then written to the systems your team already uses as the call ends.

Captured on the call

  • Still interested: yes, later or no
  • Updated contact details
  • Current requirement or role preference
  • Updated timeline or availability
  • Consent to further contact, or an opt out
  • Booked next step, if any
  • Recording, transcript and summary

Then, in your systems

  • Records refreshed in your CRM or ATS through the API or connector
  • Warm leads or candidates assigned to an owner by webhook
  • Opt outs written back so they are not called again
  • Callbacks scheduled for those who asked to be called later
  • Campaign outcomes summarised by disposition
People stay in charge

When does a person take over?

When someone is ready to talk about a specific vehicle, property or role, the agent transfers them live to the owner of the record. A team lead can follow campaign progress and join any call from a browser to take over.
Whisper, join or take overBeyond live transfer, someone on your team can open any call in their browser and whisper to one side, join the conversation or take it over, with no redial. How the audio bridge works

Database Re-activation questions

Which records should we re-activate first?

Start with the segment where an updated record is most valuable to you: recent enquiries that went quiet, past applicants with skills you are short of, or customers due for an upgrade. Xebit runs whichever list you choose as a campaign, and the outcomes show you which segments are worth calling next.

How do we avoid calling people who do not want to hear from us?

Your list goes in with the exclusions you already hold, and the agent asks for consent to further contact on every call. Opt outs are written back to your CRM or ATS through webhooks, so the next campaign leaves them out. Calling windows, retries and pacing are set by you.

Can a large database run without swamping the team with transfers?

Yes. Pacing controls how many calls run at once, and you choose whether warm contacts are transferred live or booked for a callback. Xebit has sustained 150,000 calls a day on a single VM in production, so the limit is usually how many conversations your team wants to receive.

SEE IT ON YOUR WORKFLOW

Bring your script. We will run it live.

We will set up the database re-activation workflow on a live agent, connected to a test copy of your systems, so you can hear the call and see the record it leaves.