Jobs and background work
Understand how Polaris Operator continues tasks, handles errors and prioritizes important work.
Jobs let Polaris Operator run tasks in the background, even after a conversation has ended.
This helps when a request does not need to finish immediately in the chat, but still needs to be completed in an organized and trackable way.
When jobs are used
Jobs are useful for tasks like:
- Processing requests after a conversation.
- Sending notifications.
- Preparing tasks for a team.
- Syncing information with another tool.
- Running scheduled automation.
How to configure them
- Define which task should continue in the background.
- Decide whether the task is critical, standard or less urgent.
- Add approval if the task can affect a customer.
- Test what happens when information is missing.
- Review history before enabling more volume.
How Polaris coordinates work
Polaris can continue a task, record if it fails and try again when it is safe to do so.
The goal is that users do not have to wait on screen and your team can review work status if something does not complete.
Work priorities
Polaris can treat some work as more important than other work:
- Critical: tasks needed for continuity, such as important reviews or approvals.
- Standard: everyday automation.
- Less urgent: bulk, repetitive or lower-priority processes.
If a workspace reaches certain Operator limits, Polaris tries to reduce less urgent work first before affecting important actions or human approvals.
Job examples
| Job | Typical use |
|---|---|
| Prepare appointment | Continue a booking request |
| Send notification | Alert an internal team |
| Create task | Support follow-up |
| Review request | Prepare something for approval |
Tracking and errors
Each job records its status, attempt history and relevant errors to make follow-up and support easier.
This makes it clear whether a task completed, needs review or needs a person to continue the process.
What to avoid
- Using jobs for tasks that need an immediate response.
- Running bulk processes without clear priority.
- Not defining what happens when a job fails.
- Hiding errors without notifying the team.
Related modules
Jobs often continue work started by Actions, Booking, WhatsApp or Web Widget.
They also work with Approvals when a task needs human review before completion.