Help Center

Client Packets: A Branded Resource Page Built for One Client

Updated August 13, 2026

A Client Packet is a hosted, branded page built for one named client — a buyer you just signed, or a seller preparing to list. It carries the resources they need, you email them their private link, and you can see what they actually opened. If they forward it to a friend, that friend's interest is credited back to them.

Who can use it

Client Packets are paid only — there is no free tier.

  • Free seat — locked. Ace explains the tier rather than showing an empty builder.
  • Regular seat — 5 packets.
  • Pro seat (or Ace Trove) — 50 packets.

Where to find it

Admin: Capture → Client Packets tab. Agents: Client Packets in the Ace Companion. Packets are served at /p/<packet id>.

Building and sending one

  1. New packet → Buyer or Seller. The template differs by side.
  2. Name the recipient — their name, email, phone, and the Follow Up Boss contact they map to.
  3. Review the item cards Ace composed. Only tools your account actually has live are attached, so the packet never promises something you don't offer.
  4. Add your own material — attachments, links, a calculator block, a checklist, and a personal note.
  5. Send it. Ace emails the recipient their own private link.
  6. Watch engagement in the packet's engagement drawer as they open sections.

This is the part worth understanding before you share anything.

  • The recipient's link is the one you emailed them. Their activity is attributed to them and written to their Follow Up Boss timeline. The recipient is never gated — a forwarded copy of their own link, a second device, or a bookmark all render the whole packet.
  • A share link identifies whoever forwarded it. A new visitor arriving on one sees the packet and a soft invitation to get in touch; if they do, the introduction is credited back to your client.
Simply opening or scrolling a packet does not write a note into Follow Up Boss. Ace records engagement for the drawer, but it deliberately keeps low-signal browsing out of your CRM timeline.

Honest limitations

  • Packets are not embeddable. They are a hosted page for one person; there is no iframe mode.
  • A packet with no assigned owner sends only the admin notification — nobody gets a Companion alert for it. Assign an owner if you want the agent notified.
  • A packet that has captured leads can’t be deleted — archive it instead. The delete is refused so captured records are never left without a parent; the delete dialog offers Archive, which stops the page, frees the slot, and keeps the leads attached. A packet that never captured anyone deletes normally.
  • Stored lead records do not expire on their own. The records carry an expiry marker, but nothing automatically purges them — deletion requests are handled by hand. Never tell a client their data auto-deletes on a timer.

Frequently asked questions

Can I try a packet on a free seat?
No — packets need a Regular or Pro seat, or Ace Trove.

My client says the link doesn't work.
Re-send from the packet; that re-issues their link. If they forwarded their own link to someone else, that person sees the full packet too, which is expected.

Can I reuse a packet for a second client?
Build a new one. A packet is bound to one named recipient — that's what makes the engagement and attribution meaningful.

Where do packet leads show up?
In Capture → Leads with everyone else, filterable to Client Packets.

Last updated: August 2026

Was this article helpful?