Questions, answered plainlyQuestions, answered plainly.

Companies whose salespeople work in the field: reps who visit customers, and the managers who need to see what happened. It was first built for a field-sales team in Riyadh.

There is no self sign-up. An administrator invites each person from the admin console with a role. The invitation link works once, for 72 hours.

Your company's own space in Zaps, at its own address, with its name, logo and colour. Data in one workspace is never visible from another.

Companies can be added one by one or imported from prospecting searches, and duplicates are caught: Zaps tells you whose the company already is. To move a larger set of existing records, talk to us.

No. Modules such as commerce, inbox, prospecting or attendance are switched on or off per company. A module that is off disappears for everyone.

Yes. Press ⌘K or Ctrl-K and ask Zaps how to do something. It answers in your language and can walk you through the screen step by step.

An on-site meeting has a pinned location and a radius of 50, 100 or 150 m. The check-in sends the phone's position once and records the distance. Outside the radius, it needs a reason and someone else's decision.

No. Working-hours tracking is off by default. When your company switches it on, it still needs your own consent, and it records only during working hours on working days. You can withdraw at any time.

No. Only you can answer. No administrator, manager or setting can consent on your behalf.

You, and people whose attendance reach includes you, such as your supervisor. Anyone else gets "not found".

Track points are deleted after 90 days by default. Your company can choose up to 365 days.

No. Nobody has a permission to read someone else's mailbox, administrators included. Colleagues see a thread only when it is linked to a record they can see, and then only the participants, times and, by default, the subject. The body only when you share that thread.

Gmail, Outlook and Microsoft 365, and other mailboxes over IMAP/SMTP with an app password, including Yahoo, iCloud, Zoho, Fastmail and Exchange.

No. It summarises, drafts and suggests next steps. Nothing is sent or created until you press Send or accept a suggestion.

Your company chooses. Zaps can use Google Gemini, Anthropic Claude, OpenAI and Groq for summaries and answers, and Groq, Gemini, OpenAI or ElevenLabs for transcription, each with your company's key. Without a key, the AI features say they are not set up.

Disconnecting removes your mail from Zaps. With Google, the grant is also revoked unless your calendar uses the same sign-in.

Yes, phase 2. Zaps can sign, clear standard invoices and report simplified ones once your company has onboarded with FATOORA. The flow was tested against ZATCA's sandbox.

Exactly one system, your choice. Either Zaps reports and Odoo keeps the books, or Odoo issues and reports and Zaps shows Odoo's QR code. Zaps refuses a setup that would report the same invoice twice.

Odoo 16, 17 and 18, self-hosted or Odoo Online, through Odoo's documented external API with an API key.

Zaps never deletes anything in Odoo. It rewrites a quotation only while it is a draft or sent there, and an invoice only while it is a draft.

Only if you want it. Quotations, orders, invoices and credit notes are a module your administrator switches on.

Yes. Arabic and English are equals: every screen in both, right-to-left and left-to-right. Each person picks their language.

Yes. Draft minutes can be written in English or Arabic, Ask Zaps answers in the account's language, and email drafts follow the language of the thread.

Yes, for Android and iOS. It is coming soon to the app stores. Until then, the web portal works in your phone's browser and can be installed on the home screen.

No. The web portal runs in any modern browser and can be installed as an app. The admin console is on the web too.

Your organisation's, not the device's, so a day means the same thing to everyone on the team.