Handle requests marked “E-mail not verified”
Why a request is marked “E-mail not verified”, how the customer confirms it, and how spam and blocked senders work.
Anyone can type an e-mail address into your web form, widget or chat. When that address belongs to a customer you already have, and the sender has not proved it is theirs, Aoun files the request under that customer but marks it E-mail not verified. This stops a stranger from reading a customer's history by borrowing their address.
Who counts as verified
A sender is verified when they:
- sign in to the customer portal with the code sent to their address,
- are signed in on your website and the widget sends a valid signature (see Verify signed-in visitors),
- answer Yes, it was me in the confirmation e-mail,
- write by e-mail and their message passes their domain's sender checks (DMARC). Mail that fails them is marked too.
An address Aoun has never seen is not marked: there is no existing customer to protect yet.
What you see on the ticket
The ticket and each message sent this way show E-mail not verified. The name the sender typed appears as Name given: …; the customer's own name is never changed. The ticket gets the tag unverified-sender, so you can find these tickets in a view or a rule.
Warning
Until the sender is confirmed, share nothing about the customer: no other requests, orders or account details.
Rules do not e-mail the requester about such a ticket. The sender never sees the customer's other tickets.
How the customer confirms
Aoun sends the real address one e-mail: Did you send this request? The link works for 7 days. Opening it changes nothing until the customer answers:
- Yes, it was me removes the mark, and the widget conversation it came from becomes verified.
- No, it wasn't me tags the ticket
not-me, marks it as possible spam and ends the sender's widget sessions.
A customer who is signed in to the portal can also answer on the request itself. To avoid flooding anyone, Aoun sends at most one of these e-mails every 10 minutes, and five a day, per customer.
If you checked who the person is another way, for example by phone, select Mark sender as verified in the notice at the top of the ticket. This needs permission to change tickets.
Mark as spam
When you choose Mark as spam on an unverified ticket, Aoun blocks the sender, not the customer whose address was used: their IP address and widget session are blocked for 7 days. The ticket is closed and tagged spam.
The dialog also offers Also block with the customer's address. Turn it on only if you are sure: it refuses their e-mail and requests and signs them out of the help centre. On other tickets, the requester is blocked by default only if they were never verified and have no other ticket.
Blocked senders
Go to Settings, then Security. Under Blocked senders you see each blocked IP address or widget session, its ticket, and when the block ends. Select Lift block to let them write again at once. Every lift is recorded in the audit log.
This page is for admins and roles that may manage settings.
Was this article helpful?
Related articles
- Verify signed-in visitors in the widgetSign your users' e-mail addresses on your server so that widget messages from them count as verified, and optionally require it.
- Portal, web form and widgetLet customers contact you and follow their requests without an account.
- Answer a ticketReply to customers, write internal notes, and choose the status when you send.
Still need help?
Write to the Woosool team. Sign in with your Woosool Account and we reply by e-mail and in My requests.

