Why Dazza Follow-Up Is Being Built to Connect to the Tools You Already Use
The best follow-up system in the world won't help much if you have to remember to feed everything into it.
This is probably the most important part of where Dazza Follow-Up is heading.
DFU can already handle follow-ups created directly inside the app.
That's useful.
But businesses don't work inside one app.
A new enquiry might arrive through a website.
A quote might live in accounting software.
A customer reply might arrive in email.
Another loose end might begin somewhere else entirely.
If the person has to remember every time that something should also be entered into the follow-up system, we've only moved the memory problem.
That is why connectors are becoming a major part of the DFU development work.
Website enquiries
One of the connection paths already built and proven is website form intake.
We've been using the Dazza Does It For You Wix website as the working environment.
Appropriate new form submissions can become follow-up information rather than relying on somebody remembering later that an enquiry arrived.
The website stays the website.
DFU handles the loose end.
That separation is important.
Dazza Books
We've also built the connection between Dazza Follow-Up and Dazza Books.
This gives DFU a controlled way to recognise appropriate quote and invoice follow-up obligations without turning DFU into accounting software.
Dazza Books remains responsible for the financial record.
DFU remains responsible for remembering the follow-up.
Again, each system keeps doing the job it was built for.
Email is another obvious source of follow-up work.
Zoho Mail integration has already had substantial development and testing.
The remaining work includes proving and refining the real customer connection experience and live provider behaviour.
That distinction matters.
“Code exists” is not the same thing as “finished product available to customers”.
We intend to keep being clear about that.
And more connections are being developed
This is where DFU is now expanding.
There are many more potential systems that could create useful follow-up signals, and additional connector work is under development.
I'm deliberately not publishing a giant logo wall claiming DFU works with everything.
That would be easy marketing.
It wouldn't be accurate marketing.
As individual integrations move through development, connection, testing and verification, we'll be able to say more about them.
For now the direction is clear:
DFU should increasingly be able to collect the loose ends from the tools a business already uses.
Connect — authorise — done
There's another rule behind this work.
Connecting software should not require the average small-business owner to understand API keys, webhooks, secret tokens or background schedulers.
That is our problem.
Not theirs.
The customer experience we are working towards is much simpler:
Choose the service.
Connect it.
Authorise it where required.
See that it is connected.
Carry on working.
The complicated infrastructure stays behind the scenes where it belongs.
This is one reason there isn't a release date
Every new connection adds more than another button.
It brings authentication, security, different provider rules, error handling, reconnect behaviour and plenty of strange real-world edge cases.
Those things need to work properly.
So DFU remains under active development.
We have working foundations.
We have proven integration work.
And we now have a much larger connector program being developed around it.
I'd rather keep building that carefully than announce a date simply because marketing likes dates.
Tomorrow I'll wrap up the week with a clear look at what has actually been built, what is still being developed and what happens next.
Comments