For business

Birthday treats customers actually asked for.

Customers opt in, you send one great treat, and you never touch their email or birth date. For shops, brands, teams and their agents.

What are you?

How it works

  1. 1Customers connectThey scan your QR code or tap Connect on your page.
  2. 2They opt inBirthday treats are off until a customer turns them on.
  3. 3You celebrateA heads-up before the day, one treat, straight to their birthday inbox.

Who it’s for

Local shops

A QR code on the window. No app, no spreadsheet, no customer logins.

Multi-location brands

Treats matched by city/state, synced to your CRM with webhooks.

Company teams

Birthday and work-anniversary alerts in Slack or Teams.

Agent-first birthday wishes

Your agent and your customer’s agent talk over MCP. Nobody sends anything the customer didn’t approve.

  1. The customer opts in to your treats.
  2. Your agent asks who has a birthday coming up and gets first name, days until and shared likes. Never the email or date.
  3. Your agent proposes one treat.
  4. The customer’s agent shows it, and the customer approves.
  5. It lands in their birthday inbox, or your own channel if they allowed it.
// Brand's agent -> POST /brand-mcp (brand key)
list_upcoming_connected_birthdays()
// -> [{ customer: 812, first_name: "Maya", days_until: 6,
//       likes: ["al pastor"], channel: "inbox" }]   // no email, no date
send_birthday_offer({ customer: 812 })   // one treat per birthday

// Customer's agent -> POST /mcp (customer's own token)
list_birthday_offers()                  // -> Bill’s Tacos: Free birthday taco
approve_birthday_offer({ offer_id: 77 }) // needs the customer's OK

Why we built it

Placeholder: set BEN_TWEET_URL and BEN_TWEET_TEXT

Ben @ben
My AI agents know everything about me. My calendar, my email, my files. Not one of them ever wished me a happy birthday.
The post that started it

Why I built this, and the roadmap →

Our privacy promise

No email, no birth date

You get a heads-up and the likes a customer chose to share.

Opt-in and approved

Treats are off by default and go through the customer’s approval.

One per birthday

No blasts, no ads, no selling data. Disconnect is one tap.

Questions

Do customers need an app?

No. It works on the web: they scan, sign in with email and they’re done.

What data do I get?

A heads-up that an opted-in customer has a birthday coming up, the likes they shared, and redemption stats.

Will customers get spammed?

No. Opt-in, one treat per birthday, approved by the customer, and off in one tap.

Can I keep my CRM?

Yes. Webhooks and the API sync preferences into the tools you already use.

Can my agent run it?

Yes. Connect any MCP-capable agent with a scoped token. Every call is logged.

Make birthdays your best marketing day.

What are you?