Bridge to Requests
A Contact submission that’s actually a gift request is more useful in the Requests module than rotting in the inbox. The Bridge lets you (or AI) convert it.
Who this is for: anyone who holds the Contact Inbox capability (owners and admins always do) who also holds the Request Manager capability. Both extensions must be on.
Manual convert
- In Contact, find a message with the amber ⚡ Looks like a gift request band. AI puts it on a message it thinks is a gift request, with how confident it is.
- Click Convert to request on that band.
- The request is created straight away from the message — there is no form to review first. You see “Added to Requests.”, and the band turns green: ✓ Converted to a request, with View in Requests →.
- Open the new request in Requests (click the requestor’s name) to check and complete what AI extracted — the recipient, the items, the delivery location.
Only a message AI has flagged gets a Convert to request button. A message that is a gift request but was not flagged cannot be converted; enter it with + New request in Requests instead.
Auto-convert
If an admin has ticked Auto-convert (see Bridge settings), a flagged message is converted on its own when AI is at least as confident as the threshold (85% unless changed). It then shows ✓ Auto-converted to a request.
What you’ll see
Common issues
- Convert button missing — AI did not flag the message as a gift request, or Request Manager is off, or you do not hold the Request Manager capability.
- The new request is missing the recipient’s address — AI could not extract one. Open the request in Requests and add it.
- Where the submission goes after converting — nowhere. It stays in Contact, with its pill switched to ✓ Converted to a request (or ✓ Auto-converted to a request), and View in Requests → next to it. Contact filters on status — New, In progress, Resolved — and converting does not change status, so nothing is hidden from any view.
Last updated: 2026-06-01 · Applies to: CartonCrew v1.56+