Skip to content
Outbound setting

AI setter: find the right person, qualify briefly, book the first meeting

The anicall.io setter agent only calls contacts with a documented contact basis, identifies itself as an AI in the greeting, openly asks the front desk for the decision-maker and books qualified first meetings straight into your calendar.

See pricing

Last updated: November 2026

Honest outbound

The gatekeeper flow

The anicall.io setter openly asks the front desk for the decision-maker, states an honest reason for the call and stops calling a company after two rejections by the front desk.

  1. Ask for the person

    The agent introduces itself with your company name and asks for the responsible person – no pitch at the front desk.

  2. Honest reason

    It states the real reason for the call. No made-up appointments, no pretended acquaintance.

  3. Referral, direct line or callback time

    If the person isn't available, the agent secures a referral, the direct line or a callback time as a follow-up.

  4. Two rejections and it stops

    If the front desk declines twice (configurable), anicall stops calling that company.

  5. Decision-maker reached: qualify and book

    Only once the right person is on the line does the agent briefly present your offer, check your criteria and book the first meeting.

AI disclosure in every greeting

Art. 50 of the EU AI Act applies since 2 August 2026: the agent identifies itself as an AI assistant in the greeting, confirms it when asked and transfers to a human on request.

Lead traffic light

Calls only happen with a contact basis: consent, inquiry, callback request or existing customer. Legitimate interest only with a documented reason – and only if you enable it for the campaign.

Approval by a human

Call lists coming from the API or a CRM only start once a human approves them in the dashboard or via API.

Note: telemarketing is regulated by law (in Germany e.g. Β§ 7 UWG). The lead traffic light helps you, but you remain responsible for compliance in your market.

Lead traffic light: who may be called

Every contact needs a contact basis – without a documented reason, anicall does not start a call.

Green: consent

The contact has explicitly agreed to be called.

Green: inquiry

The contact reached out first, e.g. through your form.

Green: callback request

The contact asked to be called back.

Green: existing customer

There is an existing customer relationship.

Yellow: legitimate interest

Only with a documented reason and only if you explicitly enable it for the campaign.

Red: no basis

No call. If someone objects, the contact is blocked account-wide (lead.dnc event).

AI disclosure per Art. 50 AI Act

Since 2 August 2026, people must be told when they are talking to an AI – anicall agents say so in every greeting.

In the greeting

The agent introduces itself with your company name and calls itself a digital assistant.

When asked

If the other person asks, the agent honestly confirms it is an AI – it never denies it.

A human on request

On request, the agent transfers or offers a callback by your team.

Approval gate for call lists

Call lists coming from the API, a CRM or MCP only start after a human approves them.

Create a job

A system creates a dial job with leads and their contact basis.

Notify

anicall sends the dial_job.approval_required event.

Approve

A human reviews the list and approves it in the dashboard or via API.

Pause any time

Running jobs can be paused.

Campaign features

Campaigns only run within your calling windows, with limited retries and an account-wide do-not-call list.

Calling windows

Weekdays and hours per campaign, default Mon–Fri 9 am–5 pm.

Limited attempts

Up to 6 attempts per lead, default is 3.

Reach status

Decision-maker reached, referral obtained, callback time set or blocked by front desk – evaluated per call.

Answering machine detection

The agent detects voicemail and schedules the next attempt.

Do-not-call list

Objections apply account-wide across all campaigns.

Handoff to the closer

Qualified leads can be handed to a closer agent automatically.

Frequently asked questions

Does the AI setter bypass gatekeepers?

No. The setter openly asks the front desk for the responsible person and states the real reason. It secures a referral, direct line or callback time; after two rejections by the front desk (configurable), anicall stops calling the company.

Does the setter have to disclose that it is an AI?

Yes. Art. 50 AI Act applies since 2 August 2026. The agent calls itself a digital assistant in the greeting, confirms it when asked and transfers to a human on request.

Am I allowed to cold call?

That depends on your market. In Germany, Β§ 7 UWG requires prior express consent for consumers and at least presumed consent for businesses. The lead traffic light helps you, but you remain responsible for lawfulness.

How do leads get into a campaign?

Via CSV import in the dashboard, from anilead.io or aniCRM, or through API v2 as a dial job. Every lead needs a contact basis; jobs from the API and CRMs additionally require human approval.

Launch your first honest campaign

Import leads, set the contact basis, approve the campaign – the setter does the rest.