Picture how a lead reaches the sales team in a lot of Egyptian companies. Someone fills in a Facebook form. The marketing agency exports the form responses to a Google Sheet every morning. Someone on his team copies the new rows into the CRM, then messages each person on WhatsApp from a work phone, and writes the reply back into the CRM by hand if they remember to.
That is four systems and three hand copies for one lead. Every copy costs time, and every copy is a place where a phone number gets a digit wrong or a lead gets skipped because the sheet was sorted differently that day.
That company doesn't need another tool. It needs the tools it already has to stop depending on someone retyping between them. That, and nothing grander, is what CRM integration is for.
This guide covers what integration really means, which connections to make first in Egypt, what a custom integration project involves when you need one, and how to tell a good integration partner from a risky one. If you're still choosing the CRM itself, start with our buyer's guide to CRMs in Egypt and come back.
Three things that get called "integration"
The word covers three different things, and knowing which one you're being sold saves money.
Native connectors. The CRM already knows how to talk to the other system. You log in, grant permission, and data starts flowing. WhatsApp through Meta's Cloud API, Facebook lead ads and Google Calendar are typical examples. Nobody writes code for you, and the vendor maintains the connection when the other side changes.
File and sheet syncs. The CRM reads a spreadsheet, a CSV export or a shared Google Sheet on a schedule and brings new rows in. It is less elegant than a live connection, but it's often the right answer for a marketing agency or a partner who will only ever send you a sheet.
Custom integrations. A developer builds a connection between your CRM and a system that has no ready connector, using the APIs both sides expose. It's what you turn to when a system such as an in-house ERP, a sector platform or an old database has no ready connector and a file-based transfer can't do the job. It's also the only one of the three that needs a project, a budget and someone responsible for keeping it alive.
Most companies need the first two and only occasionally the third. Being sold the third when the first would do is the most expensive mistake in this whole area.
The five connections that matter most in Egypt
The right order follows where your customers talk to you, not which systems look impressive on a diagram.
1. WhatsApp
For most Egyptian businesses this is where sales conversations live, so it comes first. The connection should use Meta's official WhatsApp Business Platform, and every message in and out should be saved on the customer's record, not on one employee's phone. We've covered how the WhatsApp connection works and what to verify in its own guide, so take that as read here. One update worth knowing: Meta's coexistence option now lets a business keep using the WhatsApp Business app on a phone while the same number is connected to a CRM through the API, so moving to a CRM no longer has to mean giving up the app your team is used to.
2. Facebook and Instagram lead ads
Lead forms should arrive in the CRM on their own, through Meta's webhooks, the moment someone submits them. Not through a daily export, and not through a sheet someone downloads. Speed matters here more than anywhere else, because a lead that fills in a form is thinking about you right now and will be thinking about someone else by tomorrow.
The better setups also send information back. When a lead becomes a booked meeting or a sale, the CRM reports that stage to Meta through the Conversions API, so your campaigns can learn which ads bring buyers rather than just form-fillers.
3. Your website's forms
Every contact form, demo request and inquiry form on your site should create a record in the CRM directly, with the page and the campaign it came from. Put spam protection in front of it, such as Cloudflare Turnstile or an equivalent. An unprotected form connected straight to your CRM is an open door for bots to fill your pipeline with junk.
4. The spreadsheets that won't go away
Somebody will always send you a sheet: the agency running your campaigns, an events team collecting names at an exhibition, a partner company passing on referrals. Fighting that is pointless. Connect the sheet instead, so new rows come into the CRM on a schedule and the first reply goes out without anyone opening the file.
5. Calendars and phone calls
Meetings, viewings and callbacks belong in the calendar your salespeople actually look at, and changes made there should flow back to the CRM. Calls matter too, because in Egypt a great deal of selling still happens on the phone. If calls with leads are logged against the lead automatically, your manager can see follow-up that would otherwise be invisible.
What can usually wait
Accounting, ERP and e-invoicing connections are real needs. If your invoices must go through the Egyptian Tax Authority's e-invoicing system, that belongs to your accounting software and whoever maintains it. But none of these decide whether a lead gets a reply today. Do them in a second phase, once the sales side works.
When a connector is enough, and when you need a build
A simple test: list every place a person currently copies data from one system to another, and how often.
If each of those copies is between your CRM and a mainstream channel — WhatsApp, Meta, Google, a spreadsheet — the answer is almost always to choose a CRM with those connectors built in, or switch on the ones you're not using yet. Paying a developer to rebuild what a product already does means paying again every time the other platform changes something.
A custom integration earns its cost when three things are true together. The system has no ready connector. The copying happens every day, not every month. And mistakes in that copy cost real money: a price typed wrong on a contract, a payment that never shows up against the customer, a stock level that tells sales a unit is free when it's sold.
A fully custom CRM is a bigger decision again. It makes sense when your process doesn't fit any product, even with configuration. That's rarer than it feels when you're frustrated with the tool you have. If you're weighing it, read how the different types of CRM compare first, because the gap is often a missing configuration, not a missing product.
What a custom integration project actually involves
If you do need one, this is the work, whoever does it. A provider who skips any of these steps is leaving you the problem for later.
A data map. Every field that moves, where it comes from, where it goes, and which system has the final say when the two disagree. If the CRM says a customer's phone number is one thing and the ERP says another, somebody has to decide in advance which one wins.
Direction and timing. One way or both ways, and how quickly: instantly through a webhook, every few minutes, or once a night. Instant is not always better. It's more work, and a nightly sync is perfectly good for data nobody acts on the same hour.
Duplicates and Egyptian phone numbers. This is where most integrations here quietly fail. The same customer arrives as 01012345678, 201012345678 and +20 10 1234 5678 from three different sources, and without normalisation they become three people with three salespeople calling them. Agree the matching rules before a single record moves.
What happens when it breaks. Every connection fails eventually: a token expires, a password changes, the other side updates its API. You need alerts that reach a person, a log of what failed, and a way to replay what was missed. An integration that fails silently is worse than none, because everyone trusts data that has stopped arriving.
Permissions. Which account the integration runs under, and who can switch it off. It should never run on one employee's personal login, because when that person leaves, the connection leaves with them.
Testing with real data, then handover. Test with a copy of real records, messy phone numbers and Arabic names included, not ten tidy examples. At the end, you should receive documentation that another developer could pick up, and the credentials should sit in accounts your company owns.
Questions to ask an integration partner
Put these in writing before you sign anything.
- Which official APIs will you use? For WhatsApp that should be Meta's Cloud API. If the answer involves WhatsApp Web automation, a browser extension or an "unlimited sending" tool, walk away. Numbers used that way can be restricted or banned.
- Who owns the accounts? The Meta business account, the WhatsApp numbers, the ad accounts and the domain should all belong to your company, with the partner added as a user, not the other way round.
- How will we know when a sync fails, and who fixes it? Ask for the alerting setup and the response time in plain terms.
- What happens when the other system changes its API? Is maintenance included, billed per incident, or not offered?
- How are duplicates and phone formats handled? Ask them to show you, not describe it.
- Can we export all our data, at any time, in a usable format? If the answer has conditions, that's your answer.
- What do we get at handover? Documentation, credentials, and the source code if you're paying for a custom build.
- What are the running costs? Meta charges for some WhatsApp messages, and some platforms charge for API access. Know which costs are pass-through and which are the partner's margin.
Red flags
- "We integrate with everything." Nobody does, and a partner who says so hasn't thought about what integration costs to maintain.
- Your data or numbers registered under the partner's accounts. It feels convenient on day one. On the day you part ways, it's a hostage situation.
- No answer to "what happens when it fails". It will fail. The only question is whether you find out in five minutes or five weeks.
- A price with no discovery. A serious integration quote comes after someone has looked at both systems and your data map, not before.
How V Estate and Vilartech handle it
In fairness, here is what we do and don't offer, since we sell in this market.
V Estate, our real estate CRM, connects natively to the channels Egyptian property companies sell through. WhatsApp runs through Meta's official Cloud API, with coexistence so a team can keep the WhatsApp Business app. Facebook and Instagram lead ads arrive automatically, and on the higher plans lead stages can be sent back to Meta through the Conversions API. Messenger and Instagram messages share one inbox with WhatsApp on the higher plans. Leads from the company website V Estate builds come in directly, behind Turnstile. Google Calendar syncs both ways for tasks and callbacks. A Google Sheet can feed leads in about every minute, available as an add-on. Leads, properties and clients import and export as CSV or Excel. And on Android, calls with leads made on the agent's own phone are logged automatically on the top plan. Not every connection is included in every plan, so check pricing for what comes with which.
What V Estate doesn't offer today is a public API, Zapier-style automation or a connection to accounting software. Where a company needs those, or needs to connect a system that has no ready connector at all, that's custom work, and it's what the rest of Vilartech does. Our software services team builds integrations and internal systems for Egyptian businesses. Project pricing for platforms that need API integrations starts at the Growth tier on our pricing page, and every quote comes after a look at both systems.
If you already know how your data should move, tell us which systems you want connected and we'll tell you honestly whether it needs a build or just a setting.
Start with one week of counting
Before you talk to any provider, us included, spend one week writing down every time someone on your team copies data from one place to another: what, from where, to where, and how long it took. Most companies are surprised by two things. The list is longer than they thought. And the top two or three items on it are ordinary connections that a CRM with the right connectors already does, with no project at all.
That list is also the best brief you can hand an integration partner. It turns "we need integration" into a specific job with a specific price.