Blocked Issues Trigger Escalation Readiness
Work gets blocked and frustrated team members are reaching out. Your escalation agent is ready to take their calls with blocker context and next steps - not fumbling for details.
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 get blocked and people are frustrated. You're not ready to discuss it. Escalation calls are disorganized. People lose confidence in your ability to unblock work.
- Escalations are handled immediately instead of creating more frustration
- Your agent has full context so conversations are focused on solutions
- Blocked work gets unblocked faster when escalations are handled smoothly
Setup
Build it in a few focused steps.
- 11. Connect Linear and Bolna to Notis.
- 22. Create an automation: 'When an issue is marked blocked, activate my escalation agent to receive calls about this blocker.'
- 33. Tell Notis to include the blocker description, who it affects, and estimated resolution time in the agent's context.
- 44. Set the trigger to 'Issue updated' (blocked status) and choose a notification channel.
- 55. Test by marking an issue as blocked and verify your escalation agent is activated.
Questions about this workflow
Should the agent proactively call the assignee when something is blocked?
This setup makes the agent ready to *receive* escalation calls. To proactively notify, ask Notis for a separate 'blocked item notification' automation.
What if the issue gets unblocked quickly?
Tell Notis: 'Deactivate the escalation agent when the issue status changes from blocked.' Notis removes it from escalation duty automatically.
Can the agent suggest solutions to the blocker?
Yes. Tell Notis: 'If caller mentions the blocker, suggest [solution 1], [solution 2], or escalate to [person].' Notis empowers the agent.
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.