# Time Conditions webhooks

> Category: Premium Features
> Canonical URL: https://crazytel.com.au/knowledgebase/article/time-conditions-webhooks

See which route each call took through a Time Condition, including schedule checks and how the call ended.

#1 Time Conditions webhooks




Time Conditions route calls differently depending on the time of day, day of week and public holidays. Webhooks let you see which route each call took.




#2 Events




EventWhen it is sent


time_condition.startedA call arrived at the Time Condition.
time_condition.routedYour schedule was checked and a destination was chosen.
time_condition.completedThe call finished normally.
time_condition.abandonedThe caller hung up before the call finished.
time_condition.failedThe call could not be completed.




#2 Example message




{
  "event": "time_condition.routed",
  "occurred_at": "2026-06-12T04:00:01Z",
  "account_code": "295327",
  "caller_id": "61400111222",
  "original_did": "61298786988",
  "time_condition": {
    "uuid": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Office hours router"
  },
  "call": {
    "uuid": "550e8400-e29b-41d4-a716-446655440004",
    "status": "routing",
    "started_at": "2026-06-12T04:00:00Z"
  }
}
The routed and later events can also include which rule matched (matched_rule_name), whether the default route was used (default_used) and where the call was sent (destination_summary). This makes it easy to check your after-hours routing is working as expected.




You can see this example in the portal under Premium Features > Time Conditions > Usage > Webhook sample.




#2 Security




If you set a secret, each request includes:




X-Crazytel-Signature-256: sha256=<signature>
User-Agent: Crazytel-Time-Conditions-Webhook/1.0
See Verifying webhook signatures.




#2 Cost




Email alerts and webhooks are free on the platform. SMS alerts are billed per segment.