ZAWAT← What We Build

Services · 06

Integration & Support

We connect your tools and keep them running — third-party, payment, SMS, email, and WhatsApp integrations, backed by dependable ongoing support and maintenance.

Integration is a data question before it is a technical one

Connecting two systems is rarely difficult. Deciding what should happen when they disagree is. If the CRM and the accounts package hold different addresses for the same customer, which one wins, who is allowed to change it, and what happens to the record that loses? Answer that and the integration is straightforward work. Leave it unanswered and you get a synchronisation that appears to succeed and quietly corrupts both sides. So we start by naming the system of record for each shared fact, then choose the pattern — scheduled sync, event-driven, direct API, or a middleware layer — to fit that decision rather than the other way round.

Messaging channels are not interchangeable

WhatsApp, SMS and email look like one requirement and behave like three. Each has its own delivery guarantees, its own cost per message, its own rules about what may be sent unprompted, and its own consequences for getting that wrong. WhatsApp in particular is governed by template approval and time windows that shape what your system is able to do, not merely what you would like it to do. Choosing the channel per use case — a delivery notification, a one-time code, a monthly statement — and designing a fallback for each, is what keeps the messaging working when one provider has a bad day.

Support that is defined rather than implied

Most support arrangements fail on definition, not on effort. What counts as an incident, how quickly someone responds, how quickly it is expected to be fixed, who is called at nine on a Friday evening, and what is included versus billed — these should be written down before they are tested by an outage. We would rather agree a narrow scope precisely than a generous one vaguely. Alongside it, the unglamorous work: updates applied on a schedule, monitoring that tells you before a customer does, backups verified by restoring from them, and a record of changes so that the question after an incident has an answer.

What's included

Common questions

Can you take over a system somebody else built?
Often, yes. The first step is an assessment of what actually exists — code, environments, credentials, dependencies and documentation — because the honest scope of a takeover cannot be quoted from a description of the system alone.
What happens when a provider changes their API?
It should be noticed by monitoring rather than by a customer. Integrations are built with retries, error handling and alerting on the assumption that external services will change or fail, because eventually all of them do.
What does ongoing support include?
Whatever is written into the agreement, which is the point. Response and resolution targets, hours of cover, what counts as included work, and how anything outside it is handled — all agreed in advance rather than negotiated during an incident.

Further reading

Tell us what you want to build. We'll design the software and systems to get you there.

Start a Project

What We Build

Custom SoftwareWeb DevelopmentAI & AutomationBusiness SystemsE-Commerce Technology