Skip to Content
ModulesRequestsCreating a request

Creating a request (admin side)

Most requests come in via the public form. This guide is for the cases where a teammate enters one on behalf of a caller, a partner org’s referral, or a paper-form intake.

Requests arrive through three channels: the Public form, Email to your inbound address (see Inbound email), and Manual entry, which is this page. All three create the same kind of request.

Who this is for: anyone who holds the Request Manager capability (owners and admins always do). It is one capability, not a read and a write one: whoever holds it can see, change and delete requests, and without it the Requests screen does not open at all.

Steps

  1. Open Requests → + New request. The form opens on ✎ Enter manually. To have AI fill it in from an email or note instead, switch to ✉ Paste email / text, paste it in, then review the fields it extracts.

  2. Fill the Requestor section (the person asking):

    • Name, contact, consent tier.
    • If they exist already, the typeahead picks up the existing Requester record.

  3. Fill the Recipient (the person the gift is for; may be the same as the requestor):

    • Name, age, gender (with Self-describe option).

  4. Items requested — add one row per item. Each row has a Category, a description (e.g. “Winter coat”), and — for sizeable categories like Clothes and Shoes — a size dropdown. The category list and which categories show a size are managed in Item categories.

  5. Delivery Location — at minimum city + state. Full address required if Shipping is By Post/Courier or Organization Will Deliver.

  6. Shipping method is the dropdown under Delivery Location, next to the delivery date and time. Choose one of:

    • By Post/Courier — mailed to the recipient’s address.
    • Organization Will Deliver — your team drops it off.
    • Requestor Pickup — they collect from you.

    Below it, the delivery instructions box (free text) takes anything the driver or courier needs (e.g. “leave with the front desk”, gate code).

  7. Notes — any ambiguity, missing info, or assumptions, free text.

    There is no campaign field on this form. A request is tied to a campaign only when it arrives through a campaign link to the public form — see Campaign link & codes.

  8. Save request. The request appears at the top of the Requests list, open, not picked and not done.

After it is saved

There are no workflow tabs. A request moves along with the two toggles on its row: mark picked when the items are picked, mark done when it is handed over. Marking it done removes the recipient’s name at once (see Snapshotting PII). The whole review flow is in Requests.

What you’ll see

Common issues

  • “Location must include at least City and State” — same validation as the public form; type the city + state, not just a ZIP.
  • Save blocked on Shipping = Post but no full address — that combo requires the full street address.
  • Requester typeahead doesn’t find the person — they may not exist yet. Save the request; CartonCrew creates a new Requester record from the form data.
  • No Category / Size dropdown on items — categories haven’t been set up yet (or the chosen category isn’t sized). Add or edit them in Item categories. On the public form, items are grouped by category — pick the category once, then add each item line under it.

Last updated: 2026-06-09 · Applies to: CartonCrew v1.110+

OverviewItem categories