What Does ‘Connected’ Actually Mean for Dazza Follow-Up?
A green Connected badge is easy to draw. Making the connection trustworthy is the actual job.
There is a temptation in software to treat the connection screen as the finish line.
Click a button. Authorise an account. A green tick appears. Job done.
For Dazza Follow-Up, that is only the start.
Connected has to mean the right account
The first question is basic but important: whose information did we just connect?
A small business owner may have more than one email account, more than one business file, test accounts, old accounts or different organisations under the same provider.
DFU cannot simply see that access was granted and assume it knows which business or records belong in the follow-up workflow.
The connection has to preserve ownership and business boundaries properly.
It also has to survive real life
Connections expire. Passwords change. Providers rotate tokens. Permissions get revoked. A user disconnects one service and reconnects another.
That is normal.
A useful integration has to handle those events without silently dropping follow-ups or quietly reconnecting to the wrong thing.
The simple customer experience we are working toward is still Connect → Authorise → Connected.
But all the awkward work underneath that simple flow still has to be tested.
Reading data is not the same as understanding a follow-up
This is where DFU becomes different from a generic integration catalogue.
Being able to read an invoice does not automatically tell you whether a follow-up is required.
Being able to see an email does not mean every message should become a task.
Being able to receive a website form does not mean every submission belongs in the same queue.
The connection needs enough context to identify a genuine loose end without turning everything it sees into noise.
When DFU is unsure, uncertainty matters
One of the design principles we keep coming back to is that the software should not quietly guess when it is not sure.
If DFU cannot safely determine the person, responsibility or follow-up state, that uncertainty should be surfaced rather than hidden.
The person using the system stays in control.
That is a less flashy promise than “AI does everything for you”, but it is much more useful in a real business.
So are the connections finished?
No.
There is substantial connection work already built and more connector development underway, but the wider set still needs proper end-to-end testing before we treat it as release-ready.
That is why DFU is still under development and why we have not announced a release date.
For us, connected will eventually need to mean more than authorised.
It needs to mean the right source, the right owner, the right loose end and behaviour we can trust.
Comments