When a workflow's Ask a person step needs you, the question lands on your Requests page in Bizomate and as a notice under the bell — and, if you have not answered within the time the step allows, by email too. Wherever you see it, you answer it in Bizomate.

Requests reach you in the Bizomate app — the Requests page and the bell — on Slack, Microsoft Teams, Telegram or SMS if you linked them, and by email. WhatsApp and RCS come next. By SMS, reply with the number of an answer. On Slack, Teams or Telegram, select an answer's button under the message and it counts at once; a button marked (in Bizomate) opens the request here instead. See Choose where you answer requests.

Who can do this

The people the step asks — members of the workspace, or the person who started the run — signed in to Bizomate in the company the request comes from.

Steps

On the Requests page

  1. Select Requests in the top bar. The number beside it is how many are waiting for you in this company, and the page says, for example, 2 waiting for you — or Nothing waiting for you.
  2. Each request shows the question, then the workflow, the run and when it was asked — for example Vendor payments · run #877 · asked 10:42:05 — and its state: Waiting; Needs a second step, when the amount is at or above an answer's limit; Answered, with the answer and where it was given; or No answer.
  3. Select a request to open it.

From the bell or an email

  • The bell — the notice reads Consulace asks, with the question. Select Answer.
  • Email — the email reads Consulace asks you, with the question and a button for each answer. Each opens Bizomate to confirm. A forwarded email can't answer for you. Select an answer: the request opens in Bizomate with that answer already chosen.

Sign in if Bizomate asks you to.

Give your answer

  1. Under Your answer, choose an answer. An answer marked asks for a reason needs one; asks for a reason (optional) means you may leave it out.
  2. If the answer asks for a reason, type it in Reason — Sent with an answer that asks for a reason.
  3. For Reply in words, type your answer in Your words.
  4. Select Send answer. An answer can't be changed once it's given — the run goes on down that path. Not now takes you back to your requests without answering.

The page says Answered — …. The run carries on.

When the answer needs confirming

An answer marked confirm with your passkey or second step needs confirming: the amount is at or above the limit the step sets for it.

  1. Choose it and select Send answer — or select it in the email. The page says “…” confirms from its amount, so confirm it's you. If the answer asks for a reason, type it in Reason here.
  2. Select Confirm “…” and use your passkey. Or, if you have an authenticator app, select Use your authenticator code instead, type the code in Your authenticator code, and select Confirm “…”. With no passkey, Bizomate asks for your authenticator code straight away.

What happens next

  • When one answer is enough (the step asks Any one of them), the run carries on down your answer's path straight away, and the request closes for everyone. Anyone who opens it then sees Already answered — …, by … in … at …, with the time in their own time zone.
  • When everyone has to answer (the step asks Everyone), the page says Answered. The others are still being asked. A Reject or No from anyone ends the step at once; it goes ahead only when everyone has said Approve or Yes.
  • The run records your answer — who gave it, where and when, and your reason or words if you gave them. Where is the Bizomate app, Slack, Telegram, SMS, or email when you opened the request from the email's button.
  • Your notice under the bell goes once you answer, or once the request closes.

Good to know

  • An answer cannot be changed once you have given it — the run has already moved on.
  • The email's buttons only choose the answer. You still send it in Bizomate, signed in as yourself, so a forwarded email cannot answer for you.
  • Confirming takes a passkey or an authenticator code. A recovery code does not confirm an answer. See Manage your two-factor methods.
  • Requests belong to a company. The Requests page and its count show the company you are in; switch company to see another's.
  • If you do not answer in time, the run goes down No answer, and the request says Nobody answered in time, so the run went down No answer.
  • Every request stays on the Requests page until it is answered or its time runs out, whatever else reached you.

If something goes wrong

What you see Why What to do
Already answered — …, by … in … at …. Someone answered first — or, when everyone has to answer, you already have. Nothing — the answer is recorded.
Nobody answered in time, so the run went down No answer. The step's time ran out. Tell the person who built the workflow, if it still needs an answer.
Choose an answer. You selected Send answer with nothing chosen. Choose one.
Give a reason for this answer. The answer needs a reason. Type it in Reason.
Type your answer. Reply in words is chosen, and Your words is empty. Type your answer.
That answer isn't one this request offers. The answer chosen is not on this request — from an old email, say. Choose one of the answers shown.
This answer needs your second step. Add a passkey or an authenticator app first. You have neither, and the answer needs confirming. Add one, then answer. See Manage your two-factor methods.
The passkey didn't go through. Try it again, or use your authenticator code. The passkey was cancelled or failed. Try again, or use your code.
That passkey isn't one of yours. Try another, or use your authenticator code. The passkey belongs to another account. Use your own.
That code isn't right. Check your authenticator and enter the code it shows now. The code was wrong or out of date. Enter the code it shows now.
This request isn't here — It was asked of someone else, or in another company. You are signed in to another company, or the request is not yours. Switch to the request's company. See Switch to another company.
Your answer wasn't sent, because Bizomate could not finish. Try again. Something went wrong on Bizomate's side. Try again.
You chose the wrong answer. An answer cannot be changed once given. Tell the person who built the workflow; the run has gone on down that path.