Resending an offer's access code
Issuing a new access code for a sent offer, and what stays unchanged when you do.
Resend issues a new code for an offer that’s already with your client, either because they can’t find the email or because the code has to reach somebody else. The offer itself is untouched.
Availability
Resend Offer sits at the top of the project page, in the same spot as Send Offer. The one control covers both: the first send out of Draft, and every code after that while the offer is with your client.
It shows up as soon as the project is Offer Pending. Past the Valid Until date, the button is greyed out and tells you what to do:
This offer expired. Edit the project to withdraw it to draft, adjust the validity date, then send it again.
That path issues a fresh offer number and a fresh link. See Projects and their statuses.
Sending a new code
Resend opens a short dialog, pre-filled with your main contact’s email.
Change the address if the code needs to go elsewhere, then hit Send new code. The email carries the same link as before, with a line saying this code replaces the earlier one.
Recipients
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. |
Sending to a second address is how an offer reaches another person at the account, someone who has to sign it or approve the spend, without cutting off the first.
The first accept or decline closes the offer. The other codes stop working.
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.
Withdrawing to Draft is the other route, and it releases the offer number and invalidates the link. Resending changes nothing but the code.
