Run New Zealand campaigns from your agent

It means Oppizi's whole offline stack can be driven by an AI rather than by clicking. Direct mail, Unaddressed Mail and flyering all get scoped, launched and measured in conversation. Two doors in: hand your own agent access through the Oppizi MCP, or work with Copilot, which lives inside Oppizi OS. Soleon is the agent infrastructure beneath both.

Copilot is the assistant that sits inside Oppizi OS. Ask in plain words and it answers on the spot — which channel fits the brief, who to reach, why a step has stalled, what a campaign is likely to cost. It talks you through setup and passes you to a person when it runs out of ground. Answers are drawn from Oppizi's knowledge base, so it does not make things up.

You sign in once; there are no keys to issue or rotate. From then on your assistant can draft campaigns, read performance and check pricing on request. It runs on the open Model Context Protocol, so Claude, ChatGPT, Cursor and any other MCP-capable assistant work without setup. This part is live in production.

Yes. Describe it and the assistant builds it with you — artwork attached, launch date set, checks done. Two New Zealand campaign types can be built this way: Direct Mail against a customer list you already own, and Unaddressed Mail across whichever delivery rounds you pick. Both land in In Review for a person to release.

Yes, because nothing self-launches. Anything an assistant or the API creates parks at In Review until someone on your team releases it — no print run, no postage, no charge before that. Access is a single sign-in rather than distributed keys, so who can reach your account stays as controlled as what goes out.

Yes to both. Ask how it went and back come conversion rate, revenue, ROI, reach, scans and conversions — split by city, by week, by creative, by A/B variant — nothing to assemble by hand. Ask what it costs and you get a quote for flyering or for Unaddressed Mail, plus a running figure on whatever you are drafting, so cost and setup stay in one conversation.

Yes. Every assistant capability is a plain REST endpoint too: audiences, designs, pricing, performance and campaigns are all readable, and conversions can be posted in, straight from your own systems. Your Oppizi client key travels as a Bearer token, and the host is developer-api.oppizi.com. Reference docs, SDKs and the OpenAPI spec sit at developer.oppizi.com.

Live in production now: connecting an assistant, reading performance, checking pricing. Campaign creation is enabled account by account, so ask Oppizi to switch it on for you. Copilot is already there inside Oppizi OS. Everything starts from developer.oppizi.com.

Anything between brief and board report. Build: "Set up Unaddressed Mail around our Ponsonby store with the Christmas postcard, live 10 September, then send it for review." Cost: "What do 5,000 postcards to our own customer list come to?" Report: "Break down last month's Wellington campaign by week." Status: "Which campaigns are sitting in review?" And every build still stops at In Review for a person to approve.