October 20, 2026

• Parcels for companies

#Parcels for companies

What it is. In the Parcels space, the recipient can be a company, not just a person. The parcel belongs to the company, and any of its current employees with access to the space sees it and picks it up.

Why it matters. Before, the front desk had to pick one employee for a package addressed to the company, and only that person was notified. Now the package belongs to the company: every employee with access gets the e-mail (or only the company's admins, if it prefers), and whoever is at the office picks it up. Someone who leaves the company stops seeing its parcels right away.

Where it is. In the Parcels space, Receive a parcel › Recipient: companies show up with the Company badge. The Queue gets the All companies filter. The Notify only the company's admins about parcels option is in the company record, under Administration › Members, Companies tab (owner and admin).

How to start.

1. Tap Receive a parcel and type the start of the company's name.
2. Pick the company (the one with the Company badge) and save.
3. If only the company's admins should be notified, turn the option on in its record.

Example. A package from Staples arrives for Acme. The front desk registers it for Acme; the employees see the card "For Acme" in My parcels, with the place and the code, and the first one to stop by taps I picked it up. If the company is closed, the parcel stays stored, with the Company closed badge, with no e-mail notice or reminder. Through the assistant, just say "a package arrived for Acme" (recipe 77).

#Improvements

• The member's phone goes along in webhooks and integrations. Before, events carried only the person's name and e-mail. Now they also carry the phone, when the person added one: HubSpot saves the phone on the contact and RD Station on the lead's mobile phone. See Webhooks.

#For developers

#API

• Parcel for a company: GET /api/parcels/spaces/{spaceId}/members also returns companies, with type (member or company) on each item. Registering accepts recipientCompanyId instead of recipientMemberId. The parcel gains recipientType and recipientCompany (id, name, status, removed); on a company's parcel, recipient and recipientMemberId come as null. The queue filters by recipientCompanyId and q finds by the company's name. POST and PATCH /api/companies accept parcelNoticeAdminsOnly. See Parcels › In the API.
• Phone in the payload: the member block of every webhook event becomes { id, name, email, phone, phoneCountry }. phone comes in E.164 (+5541999998888) or null; phoneCountry in ISO 3166-1 alpha-2 (BR) or null. It applies to every destination. See Webhook events.

#MCP: technical details

• search_parcel_recipients returns type; register_parcel accepts recipient_company_id (and recipient_member_id becomes optional: one of the two); list_pending_parcels and list_parcels filter by recipient_company_id.
• The current employee sees the company's parcel in do_i_have_parcels and get_parcel, with the code, and picks it up with mark_parcel_picked_up (SELF).
• create_company and update_company accept parcel_notice_admins_only, with no confirmation. See Tools · Parcels.