Recipient handover script
What to say + do when handing a bed to the person who'll sleep on it. Tested language, not a corporate script. Adapt to the relationship + community.
Before you say anything
- Listen first. If a Traditional Owner or community lead is welcoming you, let them speak. Don't cut in to explain the bed.
- Read the room. Sometimes the bed is the third thing happening (a death in the family, a new baby, a flood). The bed waits. Your timing matters more than your words.
- No clipboard. Don't hold the install logger between you and the recipient. Phone in your pocket until after the conversation.
- Sit down. Eye-level is recipient-level. Standing over a bed feels like inspection.
What to say (rough script)
Aim for three things in the first 60 seconds: this is yours, this is how it works, this is how we stay in touch.
1. “This is your bed.”
“G'day. This is a bed from Goods on Country. We made it at the Alice plant. The plastic is recycled. The canvas is heavy-duty Australian — washable, holds 200 kilos, designed for ten years plus. The poles are galvanised steel, won't rust.”
Hand them the bed if it's not already installed. Let them touch it before you talk about what to do with it.
2. “Here's how it works.”
“Five-minute setup, no tools. The two poles slide through the canvas sleeves and the holes at the top of the plastic X-legs. Push the pole in from its end, not the side, and tension holds it.”
Demonstrate once. Then let them try. If they want to pull it apart and put it back together, let them — that's the moment they actually own it.
“To wash the canvas: slide the poles out, pop the canvas off, machine wash cold or warm with mild soap, hang it on the line. Comes back like new. Don't put the poles or legs in the machine.”
3. “Here's how we stay in touch.”
Pull out your phone. Scan the QR sticker on the bed's leg.
“Every bed has a QR sticker. Anyone scans this, it opens a page just for your bed. You can give it a name — kids name beds, that's normal. You can let us know how it's going with one tap. You can ask any question, we'll get back to you. If you want a blanket or pillow, ask through here. If anything breaks, ask through here.”
Show them one tile working. The Pulse 👍 is the fastest demo.
“Or you can text us straight: +61 468 052 660. Same person on the other end. Reply STOP any time and we stop texting.”
If they want an account
Account = messages + ability to request things like blankets without retyping who you are. Optional. Most people are fine without.
- Tap “Stay in touch” on the bed page.
- Phone number, OTP code, done. 30 seconds.
- After that, all their bed's photos + messages land in /my-items.
What you do, not what you say
Install logger (admin only)
- Scan the QR. Page opens.
- You see the install logger card above everything else (admins only see this — it doesn't appear for the recipient).
- Pick the community from the dropdown.
- Type the place: family name, outstation, house number. Whatever they call it locally.
- Tap “📍 Use my GPS”. Wait for accuracy ≤30m.
- Set status to deployed.
- Save. You'll see “The asset register is updated.”
Photo (with consent)
- Ask first. “Mind if I take a photo for our records?” Some yes, some no. Some yes-but-not-of-people. Respect that.
- One photo of the bed in place is enough. Upload via the Media Room.
- Tick “Show on the public bed page” only if they're comfortable with that. Default for sensitive photos: unticked.
Cultural protocol
- Sorry business. If someone has passed in this community recently, ask if it's OK to be here today. If not, leave the beds and come back. Don't take photos. Don't name names.
- Photos of children. Default: don't. If a parent insists, only the parent in frame, not the child.
- Naming dead people. Some communities have strong protocols about naming people who have passed. If unsure, ask “is it OK to use this name in our records?” before logging anything publicly.
- In-language names. If a community leader gives the bed a name in their own language (the way Dianne Stokes named the washing machine Pakkimjalki Kari), record it carefully. Spell it back. Get the right speaker to confirm.
If something goes wrong
Bed is damaged out of the truck
Don't install. Set status to under_investigation. Photo the damage. Notes field: what's wrong. Goods will replace or repair from the next batch.
Recipient doesn't want it
That's fine. Don't pressure. Pull status back to allocated, leave the community pool to redistribute. Note the reason in the asset record if they shared it.
Bed lands in wrong house
Move it. Update place in the install logger to where it actually ended up.
Recipient asks for something we don't have
Honest answer: “I'll check when I'm back, but I can't promise.” Log it as a demand_bump via the “We need more here” tile on /bed/<ID>. Goods follows up.
Before you leave the community
- Every bed scanned + GPS-logged.
- Photos uploaded (with consent).
- Anything unusual captured in notes.
- Demand bumps logged for what the community asked for that we couldn't deliver.
- Goodbye to the people who hosted you.
After the trip
Goods staff: monitor /admin/bed-signals for the next few days. Recipients sometimes wait a day or two before scanning. Pulse spikes (3+ 👎 in 7 days per community) trigger a GHL alert automatically — but reading the signal feed yourself catches softer issues first.
Last updated: 2026-05-16. Tested at: Tennant Creek, Maningrida, Palm Island. Refine as you learn from each community — handover scripts aren't universal.