You Don't Need to Leave Your CRM to Use Backbone Anymore

The same way Stripe lets a business run payments without opening the Stripe website, Backbone now lets your CRM run the order without opening Backbone. Once you create a mandate in your CRM, the order gets placed with one click or automatically, and everything Backbone delivers, visuals, floor plans, documents, arrives straight back into your CRM, ready to use.

‍

At a glance

• Place, reschedule, cancel and track orders from your own CRM
• Automate order creation, or predefine visual packages by property type, whichever level of control your team wants
• Order only the products and prices set up for your account, negotiated or standard
• Get notified the moment something changes, as data your system can act on, not an email to read
• Receive photos, videos, floor plans and documents straight into your system, edits included
• Generate marketing copy for Instagram and LinkedIn per listing, with more formats in development
• Sync team access automatically, so it always matches who's actually on your team
• Keep using the Backbone platform exactly as it is, if that's how your team prefers to work

‍

What actually changed

Your CRM now has direct access to the same order lifecycle that's always run on the Backbone platform. That access is what's new, not the lifecycle itself.

‍

The platform isn't going anywhere. If it's how your team likes to work, nothing changes for you. This is for the agencies whose operations already live somewhere else, and who'd rather bring the engine to them than move to it.

‍

Your team syncs too, not just your mandates

The same logic applies to your team, not just your mandates. By default, adding or removing someone's Backbone access means a manual step every time your team changes, someone remembering to set up or revoke an account alongside everything else on their plate.

‍

With the Public API, that step becomes automatic instead. Add someone in your CRM, and they're set up in Backbone too. Remove them, and their access goes with it, right away, no second list to keep track of.

‍

Every update, exactly where you need it

Connect a webhook once, and your CRM knows the moment anything changes. A shoot gets confirmed, and the date, time, and the photographer's name and phone number land on the property record, no digging through an inbox. An estimated delivery date shows up the same way, and if a key handover is involved, the pickup address, time and contact travel with the order too. If the forecast turns and you need to move the shoot, reschedule it with a couple of clicks from the same record. No call to support needed.

‍

For a team running dozens of live mandates at once, that's the real shift: a record that used to need someone updating it now updates itself.

‍

Marketing copy and paperwork, handled the same way

The Public API doesn't only move photos and floor plans. It can generate the marketing copy for a listing too, and route the legal documents your market requires through the same pipeline.

‍

Trigger it for a property, choose an Instagram caption or a LinkedIn post, set a tone and an audience, and the text is delivered straight to your system alongside the visuals. A listing goes from "visuals are in" to "copy is ready" without anyone opening a blank document. More formats, brochures and landing pages among them, are on the way.

‍

Energy certificates and other required paperwork move through the same channel, so the documents your team needs to publish a listing legally arrive with everything else, not from a separate process.

‍

Three ways to trigger an order, your call

Not every team wants the same amount of automation, and the Public API doesn't force a choice. It supports three levels of control, and your team can sit wherever makes sense.

‍

• At one end, someone places each order by hand, one click, one property, pulling details already sitting in the record, so nothing gets typed twice.
• A step further, bundle whatever your team always orders together for a given property type, a one-bedroom rental, a luxury villa, into a package. One click still triggers it, but now it places the whole package instead of a single item, nothing to choose each time.
• At the other end, no one has to click at all. The rules you've set fire the order automatically, the moment your CRM records a status change you've defined, a mandate getting signed, for instance.

‍

‍

None of these levels requires the others. A team that wants a person reviewing every mandate can stay at the first. A team ready to standardize can move to the second. And a team operating at scale can let the third run on its own.

‍

Same engine. Pick your interface.

The Backbone platform and the Public API aren't two products. They're two doors into the same production network, the same photographers and videographers on the ground across Europe, the same delivery pipeline. Place an order through either door, and you can retrieve it, along with everything it produced, from both your CRM and the Backbone platform.

‍

That includes edits. The AI tools themselves, staging a room, removing an object from a photo, live on the Backbone platform. But whatever you edit there syncs back to the same CRM record automatically, no matter which door you used to place the order. Nothing lives in only one place.

‍

Which door you use day to day depends on where your team already works, not on which one we'd rather you use. If that's our platform, stay exactly where you are. If it's your own CRM, the engine is ready when you are.

‍

Read the developer documentation →

Talk to us about your integration →