A message sent. A status explained.
What our project emails contain, where replies go, and what the email status signals can tell us.
Discuss your project ↗
Recognise our correspondence
Website emails identify Alins Enterprises and use hello@alins.site. Project messages use recorded enquiry details and reviewed copy; they do not invent missing business information.
- A clear subject and relevant project context
- Known details can prefill a private enquiry invitation
- Replies go to the business mailbox
Acceptance and delivery
Accepted means the sending service accepted a request. Delivered means the receiving email server accepted it. Neither confirms inbox placement or that somebody read the message.
- Delayed delivery may need more time
- Bounced, failed or suppressed messages need review
- Uncertain sends are checked before another attempt
Reported opens
HTML emails may contain a tracking image. A loaded image can report an open, while image blocking can hide one. Privacy proxies and security scanners may load images automatically.
- An open report is a signal, not proof of reading
- Approval is confirmed through a reply or project conversation
- Contact us to discuss communication without open tracking
Keep private details private
Project access codes are not included in automatic status emails. Private invitation links may prefill details and should not be forwarded unnecessarily.
- Use your existing project portal for shared progress
- Never send a password or access code in an ordinary email
- Read the privacy page or contact us about your information
Tell us what you need.
Start with your business, your priorities and the details you know. We can discuss the rest together.
Start a project brief ↗