Standard outbound runs on its own; exceptions go to a person
Autonomy begins only after sources, profiles, content, limits and escalation rules have been approved.
A controlled process for the HR segment
The hotel approved the sources, signals, email and LinkedIn channels, talking points, limits and situations requiring a handover.
Lead handled according to the rules
The bot selects a company, checks for duplicates, qualifies the contact, completes the permitted steps and records the history in the CRM.
- actions in permitted channels
- latest status and history
- exception passed on with context
Autonomy built from modules tested in advance
The bot combines lead generation, monitoring, calibration and communication. Every action uses a known rule, source and permission.
Finds and qualifies
It retrieves leads from approved sources, checks for duplicates and applies the customer profile.
Runs the sequence
It carries out permitted actions within set limits and stop conditions.
Records and escalates
It updates the CRM and passes situations outside the rules to a person.
How does the outbound bot run active sales?
Lead retrieval
The bot uses approved generators and the latest signals.
Qualification
It checks fit, the CRM, limits and all exclusions.
Permitted contact
It carries out only the actions permitted for the channel and scenario.
Record or escalate
It updates the status, plans the next step or passes the matter to a person.
Every action has a source, rule and history
The bot acts only when it has the required data and permission. The log shows the context, operations and reason for escalation.
What does AI use?
- approved sources and profiles
- channel and sequence calibration
- CRM with statuses and exclusions
- limits, permissions and escalations
What does the team receive?
- qualified leads and managed contact
- up-to-date CRM and history
- next step or escalation
The hotel defines the exact scope of autonomy
Permissions can vary between channels and scenarios. The team can require approval for actions or stop the process.
The team grants permissions per channel, sets limits and approval points, reviews the history and can stop the bot immediately.
Only this module receives limited autonomy. It does not bypass channel rules or continue after a stop condition, and calling remains an optional extension.
Consistent outbound without losing control of the brand
Standard steps are carried out according to one policy.
Sources, decisions, messages, statuses and escalations remain auditable.
Situations outside the rules go to a person with the relevant context.
The complete process connects sources, channels and the CRM
The bot’s scope grows with the readiness of lead generators, monitoring and communication. LinkedIn requires separate permissions.
Related process elements
Frequently asked questions
Does the bot work completely unsupervised?
No. The scope of autonomy depends on the configuration, limits, approvals and escalation rules.
Can it work on LinkedIn?
Only within the permissions granted and the agreed integration method; earlier modules work in read-only or suggestion mode.
What happens after a lead replies?
The bot records the situation in the CRM and passes every response requiring a decision to a person.
Can the bot make phone calls?
Calls are possible only as a separate, approved voice extension.