Integration
DesignDeck
If the website was built on DesignDeck, the CRM behind it does not need an integration project. The two already speak, and they speak about the same person.
The claim
A DesignDeck site captures the enquiry, Treasury answers it, and the browsing history follows the person into the record.
Today
What exists now
- Forms post straight in
- The site posts to the brand's lead webhook with that brand's own secret, the same public route every other integration uses, so it inherits the same rate limiting and the same duplicate handling.
- Live inventory out
- Unit pages read a public feed, so a status change or a new photo goes live on the website without a redeploy.
- The reference code
- The site's WhatsApp button mints a short code and prints it into the message the visitor sends.
- The stitch back
- When Treasury resolves that code to a person, it tells the site which person it was, so every page read before the enquiry attaches to a named record instead of to an anonymous session.
- One brand each
- A site and a workspace are bound one to one, so an agency running six client sites is running six sealed workspaces.
Why it is worth having
The half of the story a CRM never sees
A website knows what somebody read. A CRM knows who they turned out to be. Almost nowhere are those two facts joined, because the only honest link between them is a reference the visitor themselves carried across, and almost no one mints one.
That is what the code in the WhatsApp message is. The site minted it, the person holding the phone sent it back, and everything else available at that point is a guess. A wrong guess merges two people, which is worse than knowing nothing.
For an agency
Sell the site and the system together
An agency already building client sites on DesignDeck can put the CRM underneath them without a rebuild, under its own name, on its own domain. The client sees one product from one supplier.
We invoice you once, for everything. What you charge your client is between you and them.
Asked and answered
Questions
- Does this need custom development?
- No. The site posts to a webhook and reads a public feed. Both are documented, and both are the same routes every other integration uses.
- Can a site feed more than one brand?
- No, and deliberately. A site is bound to one workspace, which is what makes it impossible for one client's enquiries to land in another client's pipeline.
- What happens if the site is offline?
- Nothing is lost on our side. The lead is created whether or not the site can be told about it, and the notification back to the site is fire and forget.
- Does this work with a website that is not DesignDeck?
- Yes. Any site can post to the lead webhook and read the public feed. The reference code and the stitch back need a little work on the site, and the pattern is documented.
Request access
Tell us how many brands you run and who needs to see them. We will walk you through the system with your names in it, not ours.
We reply within one working day. Already a customer? Sign in at app.treasurycrm.com.