> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/alerts/personal-alerts-management.md). # Personal alerts management Manage how, when, and where you receive incident alerts in Spike to suit your schedule and reduce alert fatigue. Spike gives you full control over your personal alert preferences. Configure how alerts reach you during office hours, outside office hours, and when you're away. For example, when you're out of office, you can configure Spike to stop sending alerts. You can also reassign responsibilities to another team member when you're off duty. ## Example configurations * **During office hours**: Route all phone call alerts to app notifications. * **Outside office hours**: Prefer receiving alerts via SMS, WhatsApp, or Telegram. * **Out of office**: Forward all alerts to another team member. ## Explore
Resolved incident alertsAlerts when incidents are resolvedResolved incident alertsthumbnail-resolved-alerts.png
During office hoursCustom routing of alerts during office hoursDuring office hoursthumbnail-office-hours.png
Out of officeStep away confidently by scheduling Out of officeOut of officethumbnail-out-of-office.png
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spike.sh/alerts/personal-alerts-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.