Skip to content
Help topics · Sponsor pages and one-tap answers

How sponsor pages and one-tap answers work

The person you’re waiting on answers from an email or a private page, without an account. Here’s what they see, how a tap becomes an answer, and what stays with your team.

Updated

One-tap answers

Each ask goes to the person it’s for by email. A decision lists its options, with the one your team recommends marked. A request for help offers four answers:

  • Done: you’ve taken care of it. The team hears right away and confirms it’s cleared.
  • Hand it to someone: someone else will do it. The team hears who’s handling it.
  • Need more info: ask the team a question first. Your question goes to the team now.
  • Can’t do this: tell the team why. The team hears right away and looks for another way.

Tapping an answer opens a short confirm screen; nothing is answered until they press Confirm answer, because mail scanners open every link in an email. They can add a note, and “Hand it to someone”, “Need more info”, or “Can’t do this” asks for a few words. Each button works once and for 7 days, and their page always has the same question ready to answer.

Their page

Every email carries a link to their own page for the project. It shows, depending on what the project has:

  • Progress on each deliverable, never a count of tasks.
  • Your help moves these forward: the asks waiting on them.
  • What the team is clearing: blockers your team chose to share.
  • Cost of waiting on any blocker: what a delay would cost, including action and document requests.
  • Risks we’re watching, and Changes to the plan.
  • Delivered: the end product of each deliverable your team delivered, to open or download.
  • Accepted, with proof: finished deliverables with the evidence behind them.
  • How does this look to you?: a place to send feedback.

On the project’s Blockers & risks page, press Help manage risks & blockers to review active tasks, owners, dates, and project context with AI. Follow the task links, edit a suggestion, then confirm its form to add it. Suggestions start team-only. Nothing is added or sent just by running the review; large projects show when only part of the work was reviewed. Built-in AI follows your plan and workspace budget.

To see exactly what they see, open the project’s Sponsor view tab. (If the project calls them something else, like client or executive, the tab uses that word.)

Deliver the end product

  1. Set the final deliverableOn the project’s Overview, open the deliverable. Under Final deliverable, press Prepare deliverable, name it, and paste its link or upload its file.
  2. Deliver itLeave Deliver it now on to send it straight away, or turn it off and press Deliver when it’s ready. The deliverable has to be shared with your sponsor.
  3. Your sponsor opens itYour sponsor gets an email that it’s ready, separate from any ask, and finds it under Delivered on their page (at the top for the first week) and in what changed.

To put up a new version, press Prepare deliverable again: it replaces the old one, which stays as evidence, and withdraws any review of the old one that nobody has answered, so send the new one for review when it’s ready. A deliverable a teammate sends you for review waits at the top of My work. Until you deliver the new one, your sponsor sees neither under Delivered. Choose Undo delivery from the final deliverable’s ⋯ to hide it again.

Signed off outside Unblockd, say in a meeting? Press Mark as delivered under the final deliverable, or choose it from the deliverable’s ⋯, which works with no final too. It counts the deliverable as done and, when it’s shared, emails your sponsor and approvers with the proof. Reopen, in the same places, undoes it.

Each piece of evidence under a deliverable or task shows who added it, when, and whether your sponsor can see it. Proof an assistant attaches starts as Team only, with a Share link on its row. Edit or remove it from its ⋯. Proof on an accepted deliverable stays until you reopen the deliverable, and a done task keeps the evidence it needs to be done.

  • Links belong to one person and one project, and stop opening after 14 days. A fresh one arrives with each email, and links in older emails keep working until they expire.
  • The first time a link opens in a browser, the page asks them to confirm it’s them with a 6-digit code emailed to the same address. After that, that browser opens their links straight away for 30 days, so a forwarded link alone opens nothing.
  • Opening a link starts a session that lasts 12 hours. After that they open the link in their latest email again.
  • An expired or turned-off link offers Email me a fresh link, sent to the same address, as long as the person is still on the project. To end someone's access, remove them from the project.
  • Remove someone from a project and their links stop working straight away.
  • Viewers follow along and can ask questions, but only approvers and the main contact answer asks.

What stays with your team

Your sponsor sees only what your team shares. Tasks, including those brought in from connected tools, stay with your team; your sponsor sees each deliverable move. A blocker opened by a tool or an assistant is team-only until someone on your team shares it.

If an ask waits, Unblockd reminds them after 3 days, then at most every 3 days and the day before it’s needed, up to 3 reminders. After that your team can nudge, extend the deadline, or escalate in one tap.

Sending asks and managing blockers

Send to on an ask emails it to the person it’s for within a few minutes, with a link to their page; asks you send close together go in one email, each with its own answer buttons. If it’s the first email they get from the project, a short introduction to your team and their page goes first. Save without sending keeps it team-only, marked Saved, not sent; press Send on the card when you’re ready, and it goes then. With nobody on their side to email yet, the ask is only saved.

While an ask is Saved, not sent, Add a file on its card attaches a brief or a comparison (up to 25 MB, 10 files) for your sponsor to read before answering; remove one with its ✕. Your sponsor sees these files, under Files from the team, only after you send the ask. Your assistant can stage files the same way, and they stay hidden until a person sends. A drafted update under Asks takes files too; they appear on your sponsor’s page once you send it, and an update with files never sends automatically.

  • One wait holding up several tasks is one blocker. From a task’s Flag a blocker, choose Already flagged and pick it, so it has one ask and one thread.
  • To take a task off a blocker that isn’t relevant to it, use the ⋯ beside the blocker on the task’s page. It stays open on its other tasks; on its only task, that removes the blocker.
  • Once your sponsor has answered, Turn into a task (beside Mark unblocked, and in the ⋯ menu) makes the follow-up task: the title, the owner, where it goes, and an optional date are filled in, and their answer comes with it. It stays reachable under Recently unblocked after you close the blocker. Your assistant can do the same with turn_blocker_into_task.
  • Remove blocker, in a blocker’s ⋯ menu on Blockers & risks, takes down one flagged by mistake. It isn’t marked unblocked: it leaves the lists and their page, an open ask is withdrawn, and History keeps a record.
  • Edit blocker, in the same menu, changes what’s stuck, its details (up to 600 characters), its cost, who can clear it and its date. Save without sending keeps the change to yourself; Save and notify the sponsor shares a blocker that’s still with your team, or emails the sponsor the updated ask.

Send your first ask today

A free trial. The people you’re waiting on never need an account.