How to add a request (and when it is an emergency)

The situation

Valhalla finds a lot, but it does not know you want to change the pricing page before the November campaign. Only you know that. The portal has one entrance for that — and a separate, red door for when something is broken.

How to add a request

1. Open the What should we solve? box: from the menu, with ⌘K, with the + button in the bottom bar (on the phone) or with Request something in the Plan.
2. Write naturally: "I want to change the pricing page — three packages, not five, and a CTA to WhatsApp."
3. Valhalla recognises it is a request, not a question, and replies with a draft: title, area (for example Experience), estimated effort, when it would land in the plan and the note "Florentin estimates it".
4. Press Send request (or Edit if you want to adjust the text first).
5. You see the confirmation: "Request sent. It appears in Plan › Being estimated; Florentin estimates it by …"

You can put a link in the text or attach a screenshot (📎) too — it helps scoping. If you prefer, press 🎙 and say it out loud.

What Valhalla does with it

A request never bypasses the plan. It goes through the same steps as any finding:

• Being estimated — as soon as you send it: Valhalla classifies it, tells you where it would land and by when Florentin estimates it (48 hours). If it matches a recommendation already open, Valhalla proposes the match to Florentin.
• Florentin is estimating it — he turns it into a recommendation with a clear objective, effort, priority and expected result.
• Became a recommendation — it appears in "Needs you" and in Plan › "Waiting for your decision" like any recommendation, with a "see it" link. You approve it, it enters the queue in its computed place, Valhalla proposes a date.
• Not taken forward — rarely, when the request makes no technical sense or contradicts something; you see it under "Not now", with Florentin's reason.

Why this way and not straight into the queue? Because a three-line request does not yet have effort, risks and dependencies. After scoping, it does — and then it competes fairly with the rest.

The "Something is broken" button

Emergencies do not wait for the queue. You find them in the same box, at the bottom: Something broken? Florentin answers within 60 minutes.

1. Open the box and press Something broken?.
2. Pick the kind: Site down, Checkout / booking failing, Tracking broken, Ads account issue (suspended, disapproved), Security incident.
3. Write the details and press Report emergency.

What happens the next second:

• The session in progress is paused; its page reads "Paused · an emergency came first".
• An emergency session ("Emergency · …") is created and starts immediately; you are redirected to its page, with the live log.
• Florentin gets the alert at once and answers within 60 minutes; you see the clock on the emergency page.
• The emergency session does not consume one of the month's four sessions — the capacity stays yours.
• When the emergency is closed, the interrupted session resumes exactly where it stopped. Everything stays in the log, and the month's recap counts "emergencies resolved".