Resending an offer's access code
Your client lost the email. Send a new code without touching the offer.
Your client can’t find the email, or the code needs to reach somebody else. Resend issues a new code without disturbing the offer.
When it’s available
The Resend button sits with the offer’s actions on the project page. It only appears while the offer is Offer Pending and still inside its Valid Until date.
An expired offer needs withdrawing back to Draft, a new Valid Until date, and sending again. That issues a fresh offer number and a fresh link.
Sending a new code
Resend opens a short dialog.
Type the email address and hit Send new code. Billow sends the code to this email address.
Same person, or a different one
Email you enter | What happens |
|---|---|
The address you already sent to | Their code is replaced. The old one stops working immediately. |
Any other address | That person gets their own code. Codes already issued keep working. |
The second case is how you get an offer in front of a second person at the account, someone who has to sign it or approve the spend, without cutting off the first.
What stays the same
The offer number, the share link, and the project’s status are all untouched. Your client can use the link they already have. Only the code changed.
That’s the difference between resending and withdrawing. Withdrawing to Draft releases the offer number and kills the link. Resending changes nothing but the code.
