Your domain. Your branding. Your client's tool.
Custom share domain. Per-tenant DKIM/SPF/DMARC sender. Reply-by-email inbound parsing. Branded transactional emails. Branded OG. Powered-by removed. The boxes you actually need ticked when you sell PlanMyGrid as your agency's in-house platform.
No credit card. White-label included on Agency from day one.
Layer 1 — share host
Custom share domain via CNAME.
Point share.youragency.com (or links.brand.com per workspace) at a single CNAME. We provision and renew a TLS certificate automatically. Every share link your agency generates resolves on your host — clients never see planmygrid.com in the URL bar, in browser history, or in the OG card when they paste the link into Slack.
- Single CNAME record per workspace
- Auto-issued and auto-renewing TLS
- Per-workspace host (one custom domain per brand if you want)
- Branded favicon served on the custom host
- Branded OG image rendered on the custom host
Layer 2 — sender identity
Email sender domain with DKIM, SPF, and DMARC.
Approval-link emails, sign-off receipts, and reminders go out from notifications@youragency.com — not noreply@planmygrid.com. We use Resend under the hood with a per-tenant verified sender. You add three DNS records (DKIM, SPF, DMARC) and we handle suppression list, bounce processing, and the webhook back to your audit log.
- DKIM via two CNAMEs Resend issues per tenant
- SPF include at the apex (or _spf subdomain)
- DMARC record published with p=quarantine recommended
- Per-tenant suppression list (so a bounce on Brand A doesn't poison Brand B)
- Inbound webhook updates the share's audit log on every event
Layer 3 — inbound mail
Clients reply by email. The thread lands on the post.
Every reviewer notification carries a unique Reply-To: g-<code>@reply.youragency.com. When the client hits reply, the inbound mail gets parsed (signature stripped, quoted history removed), routed to the right share recipient, and posted as a comment on the exact post. Approval and revision-request keywords trigger the corresponding action. No login. No form. No new tool for the client to learn.
- Per-recipient unique reply address (g-<code>@reply.youragency.com)
- Signature and quoted-text stripping
- Approval keywords ("approved", "sign off") trigger sign-off
- Revision keywords ("changes", "revise") flag the post
- Inline image attachments preserved on the comment thread
Layer 4 — transactional design
Branded emails. Logo, accent, footer, voice.
All transactional emails — invite, approval request, reminder, sign-off receipt, version updated — render with your agency's logo at the top, your accent color in the buttons, your footer text, and your support email. No PlanMyGrid branding. The OG card rendered when those links are pasted into Slack matches.
- Logo upload (PNG / SVG, embedded as base64 in OG)
- Accent color in CTA buttons and link styling
- Custom footer text and support email
- Powered-by removed on Agency tier
- Branded OG card on share previews
Layer 5 — link previews
OG previews that match the host.
When a client pastes the link into Slack or iMessage, the OG card uses your agency's domain, your favicon, your logo embedded inline, and a render of the actual post the link points to. The image is generated on the custom host so the preview never leaks planmygrid.com. (Post images in OG are still being polished — a known follow-up.)
- OG host matches the custom share domain
- Logo embedded via base64 fetch
- Favicon served from the same custom host
- Slack and iMessage preview parity
White-label, layer by layer.
Most "white-label" tools mean "your logo on a share page." Here's the full stack.
| Layer | PlanMyGrid Agency | Later | Sprout Social |
|---|---|---|---|
| Custom share domain via CNAME | Yes — Agency | No | Enterprise quote |
| Per-tenant email sender domain | Yes — DKIM/SPF/DMARC | No | Limited |
| Reply-by-email inbound parsing | Yes — per-recipient address | No | No |
| Branded transactional emails | Yes — logo + accent + footer | Limited (logo only) | Enterprise |
| Branded OG card on shares | Yes | No | No |
| Powered-by removed | Yes — Agency tier | No | Enterprise |
| Per-workspace host (multiple brands) | Yes | No | No |
| Auto-renewed TLS | Yes | N/A | Enterprise |
Technical FAQ
- What DNS records do I publish for the white-label setup?
- One CNAME for the share domain (share.youragency.com → our edge host). For email: two CNAMEs for DKIM (Resend issues these per tenant), one TXT for SPF (or include in your existing record), and one TXT for DMARC. We recommend p=quarantine for DMARC so misaligned mail gets held, not rejected, while you ramp.
- Why DKIM and SPF instead of just sending from your own domain?
- Because clients trust mail from notifications@youragency.com, not noreply@planmygrid.com. DKIM cryptographically signs the mail with your domain's key. SPF tells receiving servers Resend is authorized to send for your domain. DMARC tells them what to do when alignment fails. Together: inbox placement, not spam folder.
- What does the inbound reply address look like?
- Per-recipient: g-<short-code>@reply.youragency.com. Each client recipient on each share gets a unique code. When the inbound webhook fires, we look up the code, identify the recipient and the share, parse the reply (strip signature, strip quoted history), and post the body as a pin comment on the original post.
- Can I have a different custom domain per client brand?
- Yes. White-label is configured per workspace. Run share.brandone.com on the Brand One workspace and links.brandtwo.com on Brand Two — same login, two custom hosts, two sender identities, two audit logs. Up to 20 workspaces on Agency.
- How do bounces and spam complaints get handled?
- Per-tenant suppression list. A hard bounce on Brand A's sender domain only suppresses that recipient on Brand A — it does not poison Brand B. Resend webhook events fire into our backend and update the share's audit log so you can see who didn't receive what and why.
- Do reviewers need a PlanMyGrid login to use reply-by-email?
- No. The flow is intentionally login-free. The unique reply address authenticates the recipient. They reply from the email we sent them; we know who they are because we issued the address. They never see PlanMyGrid.
- Is there an admin surface for me to monitor white-label health?
- Custom-domain status (DNS verification, TLS issuance, last-checked timestamp) is in the workspace settings page. A workspace-level admin dashboard for the agency owner is shipping shortly — currently each workspace owner sees their own setup.
Sell it as your platform. Because it is.
DNS records, sender domain, inbound parsing, branded email — set up in an afternoon. Live on your domain by tomorrow.