Overdue Work Triggers Emergency Agent Readiness
Issue due date passed. Before stakeholders track you down, your agent is ready to take their escalation call with context in hand - no scrambling.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Setup inbound call for agent
Add agent for inbound calls
Why this helps
Issues go overdue and you're not even aware. Frustrated stakeholders call your main line. You're not ready to discuss it, context is lost, conversations go badly.
- Stakeholders reach you efficiently when they're frustrated, not when you're unprepared
- Your agent has all the overdue work context so conversations are focused
- You catch escalations early instead of being blindsided
Setup
Build it in a few focused steps.
- 11. Connect Linear and Bolna integrations to Notis.
- 22. Create a Notis automation: 'When an issue's due date passes, set up my escalation agent for inbound calls about that specific issue.'
- 33. Tell Notis to include the overdue deadline, assignee, and status in the agent's call context so it's prepared.
- 44. Set the trigger to 'Issue updated' (due date trigger) and select your notification channel.
- 55. Test by creating a test issue with a date in the past and verify your escalation agent is activated.
Questions about this workflow
Should the agent proactively call the assignee when an issue is overdue?
This setup makes your agent ready to *receive* escalation calls. If you want proactive calls to assignees, ask Notis for a separate 'overdue reminder' automation.
What if the issue gets resolved before anyone calls?
Tell Notis: 'Deactivate the escalation agent if the issue is marked resolved' - Notis will remove the agent from escalation duty automatically.
Can I customize the escalation response based on how overdue it is?
Yes. Tell Notis: 'If overdue by 1 day, activate agent A; if overdue by 3+ days, activate agent B.' Context shapes the response.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Bolna. A trigger fires from one place; an action lands in another.
Linear triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
Comment Received Trigger
Triggered when a comment is received.
Fetch all batches by agent id
List all batches for agent
Issue Created Trigger
Triggered when a new issue is created.
Get all agents
List all agents
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get all phone numbers
List all phone numbers for your account
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get execution by id
Retrieve specific execution by `execution id`
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Make a phone call from agent
Initiate calls
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
Linear and Bolna, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Bolna.