Contact

Become a partner

Build on Closr, or sell it alongside your own work.

Three shapes of partnership: integrations that plug into the platform, agencies who run Closr on behalf of their clients, and resellers taking it into a market we don't cover.

What we’ll cover

01

Integration partners

You have a product our customers already use. Outbound webhooks, the site snippet, and the voice API key cover most cases today — tell us where they fall short and we'll talk about closing the gap.

02

Agencies and implementation partners

You run scheduling, outbound, or inbound on behalf of clients. Closr is built for multi-site work: portals keep each client's tracking, forms, and contacts separated under one login.

03

Resellers and regional partners

You sell into a market or vertical we don't reach. The marketing site already speaks English, Bahasa Melayu, Bahasa Indonesia, and Chinese, and the voice agent handles 97 languages.

04

What we need from you

A sentence on who your customers are, what you'd want Closr to do that it doesn't yet, and roughly what volume you're talking about. That's enough to have a real first conversation.

Replies within one business day. Tell us which of the three you are.

Start a partnership conversation

What's already open

You may not need us to build anything

Webhooks

Outbound webhooks

Automations can call an endpoint you control when a booking, form submission, deal change, or inbound message fires. Available on Sales and Enterprise.

Embed

The site snippet

One script covers visitor tracking, click capture, and embedded forms, scoped per portal so a multi-client setup stays separated.

API key

Voice integration

Drive the voice agent from your own IVR or web surface instead of the built-in widget. Available on Sales and Enterprise.

How we work with partners

The ground rules

  • We say no clearly and early rather than leaving a partnership in limbo
  • No exclusivity on either side unless there's a reason for it
  • We do not resell or share your customers' data
  • Integration work is scoped in writing before either side starts
  • Named technical contact on our side, not a shared inbox
  • Roadmap context shared honestly, including what we won't build