> ## Documentation Index > Fetch the complete documentation index at: https://docs.allquiet.app/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting & FAQs > Self-serve answers for common setup questions This page lists **common questions** and where to find answers in the documentation. For integration-specific issues, check the **Hints**, **Troubleshooting**, or FAQ sections at the bottom of the relevant [integration guide](/integrations/overview). **Inbound** topics (webhook, **Latest Payloads**, discard, correlation) are grouped separately from **alerting** (personal channels, outbound tools, **routing**) and **Live Call Routing** (inbound phone calls) so the tables stay easy to scan as we add more guides. ## On-call, schedules, and rotations | Question | Where to look | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | How do I cover **one weekend** with a single on-call person from **Friday evening through Monday morning**, and rotate **after** Monday morning (when shifts are shorter than 24h there is **no** `Handoff Time`)? | [Escalations — Weekend on-call through Monday morning](/essentials/escalations#weekend-on-call-through-monday-morning) | | How do I set **on-call times**, **overnight** windows, and **which weekdays** a schedule applies to? | [Escalations — Schedules](/essentials/escalations#schedules) | | How do **weekly rotations**, **handoff day**, and **`Handoff Time`** work? | [Escalations — Auto Rotations](/essentials/escalations#auto-rotations) | | Where is the **team time zone** configured, and how does it affect schedules? | [Escalations — Timezones](/essentials/escalations#timezones) and [Teams — Edit Team](/essentials/teams#edit-team) | | How can I have **different escalations** for **different severities**? | [Escalations — Automatic escalation](/essentials/escalations#automatic-escalation) (filter auto-escalate and auto-assign by severity); for a **separate on-call path** per severity, [route to different teams](/advanced/routing) ([shared integration setup](/essentials/inbound#how-to-use-one-integration-for-several-teams)) | | Can I have **different escalations** for **one team**? | In All Quiet, each team has **one escalation policy**. Within that policy you can define different [schedules](/essentials/escalations#schedules), [rotations](/essentials/escalations#rotations), and [rules for escalating to higher tiers](/essentials/escalations#automatic-escalation). If you need **different Tier 1 on-call**, or different **repeat** and **auto-escalation** rules for different kinds of incidents (for example by severity or service), create **separate teams**—each with its own escalation policy—and [route incidents](/advanced/routing) from [one shared integration](/essentials/inbound#how-to-use-one-integration-for-several-teams) to the right team. | | | | ## Alerting: Routing, Channels, and Outbound | Question | Where to look | | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A **new incident** exists but **nobody was notified**—what should I check? | [Inbound — New incident, no notification](/essentials/inbound#new-incident-exists-but-still-no-notification) | | How do **routing rules** affect **channels**, **outbound integrations**, **snooze**, or **discard**? | [Advanced Incident Routing](/advanced/routing) | | My **outbound** tools (Slack, Jira, webhooks, …) don't receive the incident. What could be blocking them? | [Outbound — Integrations never fire](/essentials/outbound#outbound-troubleshooting-routing) | | Why did an **outbound integration** not post or update (Slack, Jira, webhook, …)—and where do I see what it tried? | [Activity history (History tab)](/essentials/outbound#outbound-history), [Troubleshooting with activity history](/essentials/outbound#troubleshooting-with-activity-history), and [Incident — Outbound Integration Activity](/essentials/incident#incident-details-outbound-integration-activity) | | I get **no personal** alerts (email, SMS, push, voice) even though the incident exists. What could be blocking them? | [Alerting channels — Troubleshooting](/essentials/channels#troubleshooting-no-personal-channel-alerts-email-sms-push-voice) | | Why was the **wrong team** paged—or why does only one team get alerts from a **shared** inbound integration? | [Inbound — One integration for several teams](/essentials/inbound#how-to-use-one-integration-for-several-teams) and [Advanced Incident Routing](/advanced/routing) | ## Inbound: Payloads and Incidents | Question | Where to look | | ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | How does **payload mapping** work (`Discard`, `CorrelationId`, preview)? | [Inbound — Mapping payloads](/essentials/inbound#mapping-payloads) | | An **alert did not show up** the way I expected—where do I start? | [Inbound — Troubleshooting overview](/essentials/inbound#troubleshooting-missing-or-unexpected-incidents) | | I don’t see my payload in **Latest Payloads**, or how do I **open the incident** from a payload tile? | [Inbound — Latest Payloads](/essentials/inbound#latest-payloads-see-which-incident-received-the-payload) | | Why was there **no incident**—was the payload **discarded** (mapping, routing, or maintenance)? | [Inbound — Payload discarded](/essentials/inbound#the-payload-was-discarded) | | Why did the payload **update an old open incident** instead of creating a new one, or why are there **no notifications** on updates? | [Inbound — Existing incident updated](/essentials/inbound#https://localhost:3000/essentials/inbound#the-payload-updated-an-existing-incident-and-no-notification-was-sent) | | How do I use **one integration** (one webhook URL) for **several teams**, each with its own on-call and escalations? | [Inbound — One integration for several teams](/essentials/inbound#how-to-use-one-integration-for-several-teams) | | How do I route alerts from the **same source** to **different teams** by severity, service, environment, or other payload fields? | [Inbound — One integration for several teams](/essentials/inbound#how-to-use-one-integration-for-several-teams) and [payload mapping](/essentials/inbound#mapping-payloads) | | Why was **nobody paged** when the incident was created in our **Root** (central) team? | [Inbound — One integration for several teams](/essentials/inbound#how-to-use-one-integration-for-several-teams) — the Root team usually has **no on-call**; confirm **Assign to Team** [routing](/advanced/routing) ran | ## Live Call Routing | Question | Where to look | | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | Can I **buy a phone number through All Quiet**? | [Live Call Routing — Buying a number](/advanced/live-call-routing#can-i-buy-a-phone-number-through-all-quiet) | | Can All Quiet create **incidents for missed calls**? | [Live Call Routing — Incidents for missed calls](/advanced/live-call-routing#can-all-quiet-create-incidents-for-missed-calls) | | A **call went through** but **no incident** was created — what should I check? | [Live Call Routing — Call connects but no incident](/advanced/live-call-routing#call-connects-but-no-incident-was-created) | | **Nobody gets rung** when someone dials our hotline number. | [Live Call Routing — Nobody gets rung](/advanced/live-call-routing#nobody-gets-rung-when-someone-calls-the-hotline) | | The **same on-call person** always seems to be rung **first**. | [Live Call Routing — Same person rung first](/advanced/live-call-routing#the-same-person-always-seems-to-be-rung-first) | | A **second caller** ringing at the same time **always gets voicemail**. | [Live Call Routing — Second simultaneous caller gets voicemail](/advanced/live-call-routing#a-second-simultaneous-caller-always-gets-voicemail) | | We **paused** the number in All Quiet but callers **still get through**. | [Live Call Routing — Pausing in Twilio](/advanced/live-call-routing#the-number-still-receives-calls-after-“pausing”-in-all-quiet) | | More Live Call Routing setup and operational questions. | [Live Call Routing — Troubleshooting](/advanced/live-call-routing#troubleshooting) and the full [Live Call Routing](/advanced/live-call-routing) guide | ## Account, access, and billing | Question | Where to look | | ---------------------------------------------------------- | ------------------------------------------------ | | How do **trial**, **subscription**, and **invoices** work? | [Billing & Subscription](/miscellaneous/billing) | | How do I set up **SSO** (OIDC / SAML) or **SCIM**? | [Single Sign-On (SSO)](/miscellaneous/sso) | ## Still stuck? Contact [support@allquiet.app](mailto:support@allquiet.app) and mention your team name and what you already tried—we’re happy to help.