Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

We are using OpsGenie for oncall escalation - need to delay the Opsgenie message

We are using OpsGenie to call out to our on-call staff who use Zoom Phone.  The problem is the OpsGenie message starts before the call is actually picked up.  So when you answer, you are already half-way through the message.


Can we get OpsGenie to delay the start of the message?  Is there some type of delay or call handling script where we can embed delays?

1 answer

0 votes

Hi Gregg!


Justin here, from Opsgenie support - happy to help!


The voice message read aloud when a voice notification is received should only begin once a user has answered a call and pressed a key to accept that call - if your users are experiencing a different behavior (such as you described - with the first part of the message being cut off), I'd recommend that you (or the users themselves) open up a new support ticket with us here:


or start a new chat with our support team, using the in-app chat option available in the lower right-hand corner of the app. 


Once we've got a ticket open, we'll be able to coordinate some additional testing which should help us narrow down and resolve the root issue. 




Justin S

Atlassian Cloud Support

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events