Questions & troubleshooting

No. Open the link and answer. Accounts exist only for the team running the surveys.

Not yet — answers are saved only when you submit. Plan to finish a long survey in one sitting.

Not from your side. Contact the program that sent you the survey and they can help.

If the survey did not ask for your name or email, nothing in the response identifies you. Personal invitation links are the exception — those are tied to the person invited.

Yes — the survey is designed for a phone first, in both Arabic and English, and needs no app.

No. Editing always happens on a private draft; the published version keeps serving respondents until you press publish.

They stay exactly as they were, tied to the version they answered. If you renamed the underlying field, the export will show the old answers in one column and the new ones in another.

Turn off *Accepting responses* to pause it, or archive it to close it and take it out of the active list. Both are reversible; deleting is not.

Not with skip logic today — every respondent sees every question on a page. Split the survey into pages, or run two surveys, when groups genuinely need different questions.

Have them use *Forgot password* to get a code by email, or *Email link* for one-click entry. If their invitation never arrived, an admin can invite them again.

It is admin-only. The same applies to inviting people, changing roles, and the workspace brand colour — see Team & roles.

That is Excel guessing the wrong encoding, not a damaged file. Use the Excel (.xlsx) export instead, or import the CSV and pick UTF-8.

Usually not. Notifications, respondent confirmations and usage warnings are kept and retried for about twenty minutes if our mail provider is unreachable, so they arrive late rather than never. Sign-in codes and invitations are the exception on purpose — a code that turns up an hour later is no use, so ask for a new one instead.

Your survey keeps collecting. That rule has no exceptions: if file storage, email or our spam check is unavailable, answers are still accepted and stored, and the part that failed catches up afterwards. A respondent is never turned away because something behind the scenes is having a bad day.

Start with an admin on your team — most things are a permission or a setting. If it is us, write from the contact page: choose what it is about, and you get a reference number and a reply within one working day. A security issue goes the same way and is described on the security page. Fixes and new features are announced in What's new.