Skip to content
Notis

Bug Reports Trigger Ready-to-Support Agent

Bug comes in. Your agent is already configured and ready to take angry customer calls about it - not 30 minutes later when you finally context-switch.

Trigger

Issue Created Trigger

Triggered when a new issue is created.

Action

Setup inbound call for agent

Add agent for inbound calls

Why this helps

Bug reported, customer is upset, and they try to call. You're still in a meeting or heads-down on other work. Agent isn't ready. Customer's frustration grows.

  • Upset customers reach support immediately, reducing their frustration
  • Your agent is prepared with all bug details so conversations are productive
  • You stay focused on fixing the bug while your agent handles the support calls

Setup

Build it in a few focused steps.

  • 11. Connect Linear and Bolna to Notis.
  • 22. Create an automation: 'When a new bug is reported, set up my support agent to receive calls about this bug.'
  • 33. Tell Notis to include the bug description, affected version, and customer email in the agent's call context.
  • 44. Set the trigger to 'Issue Created' (for bug issues) and select Slack or email.
  • 55. Test by creating a bug report and verify your support agent is activated for inbound calls.

Questions about this workflow

Should the agent proactively call affected customers, or just be ready to receive calls?

This setup makes the agent ready to *receive* calls. If you want proactive 'we found a bug' calls, ask Notis for a different automation.

How does the agent know which customer is calling?

Notis provides the agent with the reported bug and the customer's contact info so the agent can verify who's calling and provide specific context.

What if the bug gets resolved before anyone calls?

Tell Notis: 'Deactivate the support agent when the bug is marked resolved.' Notis removes the agent from support duty automatically.

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.

TriggerScheduled

Delete agent by id

Delete an agent

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete batch by id

Delete a batch

ActionInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Fetch all batches by agent id

List all batches for agent

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Get all agents

List all agents

ActionInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

TriggerInstant

Get all phone numbers

List all phone numbers for your account

ActionInstant

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).

TriggerPolling

Get execution by id

Retrieve specific execution by `execution id`

ActionInstant

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Make a phone call from agent

Initiate calls

ActionInstant

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

Retrieve agent by id

Retrieve an agent

ActionInstant

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.