Corporate email is trust on the business card. Proposals sent from Gmail carry spam and lack-of-seriousness risk. Webify locks MX, SPF, and mailboxes together with the site on launch day.
Customer emails don't land in spam, brand trust grows.
Process
- 01
Domain
Domain is ready and WHOIS is on the correct person.
- 02
Records
MX, SPF, DKIM, and DMARC if needed are written.
- 03
Mailbox
Quota, forwarding, and device (phone/Outlook) are set up.
- 04
Migration
IMAP migration from old mailbox is planned, downtime window is written.
What’s included
- Accounts with custom domain
- Webmail, Outlook, phone
- Spam and virus filter
- Mailbox quota with backup
Who it’s for
- Those without info@ address
- Those collecting email in Gmail
- Those whose proposals fall to spam
- Those who can't close departed employee account
Why your own domain?
When customer sees "@gmail.com," they think personal line. @brand.com.tr carries the brand and makes changing the person later easier. Ali leaves, info stays.
Spam filter looks at sender reputation. Mass proposals with wrong SPF enter blacklist. Setup isn't just opening mailbox, it's DNS signature.
Legal correspondence and proposal archive should be in mailbox. Employee's personal account isn't company property; disappears when they leave.
Migration: moving without downtime
Before switching MX, new mailboxes are opened, device is tested. Then MX is switched. The reverse is one day of lost email.
Old PST / IMAP transfer takes time by size. "Finish it all last night" may not be realistic. Priority can be inbox and last year.
Forwarding (info → sales) produces bloated copies. Who will read, is written clearly. If everyone gets every email, no one reads.
Device, quota, archive
Outlook and phone stay on the same account with IMAP/Exchange rule. Wrong protocol makes double sends. One device is set up together at setup, rest is guide.
Can't send when quota is full. Large attachments move to file sharing. Telling user this from the start cuts support load.
When backup mailbox is deleted, legal archive may also go. Retention period is company policy; technically what's backed up is written.
Relationship with Google / Microsoft 365
If you want Workspace or 365, we connect them; DNS is still planned with us. "Just hosting mailbox" can be simpler and cheaper. Need is license count.
Mixed model (some Gmail, some hosting) breaks SPF. Single sender policy is targeted.
Webify sales line 0850 885 28 44 is the same team. Email down is as priority as site down.
Why are SPF, DKIM, and DMARC as important as the mailbox?
Opening mailbox isn't enough. The other side's filter asks "is this domain really sending from this server?" SPF carries allowed IPs, DKIM signature, DMARC policy (reject / quarantine). Missing trio pushes proposal email to spam; customer doesn't see you.
If some use Gmail, some hosting mailbox, some bulk tool using the same root, SPF breaks. Single sender policy is targeted. Bulk newsletter shouldn't go from this mailbox but from separate sending service—otherwise daily correspondence also gets blacklisted.
Not falling to spam isn't sold as guarantee. Correct DNS reduces risk; content, complaint rate, and purchased address list also affect. Webify sets expectation with this sentence.
Migration window and device
New mailboxes and one test device are prepared before MX. Then MX is switched. The reverse is one day of lost incoming. Old PST/IMAP transfer takes time by size; priority can be inbox and last year, ten-year archive is planned separately.
If Outlook and phone don't stay with the same protocol (IMAP/Exchange), produces double sends or lost drafts. One device is set up together, rest is step list. Webmail is enough for field; heavy desktop prefers Outlook.
When employee leaves, mailbox stops, forwarding changes, device access is cut. Proposals accumulated in personal Gmail aren't company property. Procedure is written with your HR; technical door is applied with us.
Quota, archive, and 365 / Workspace
Can't send when quota is full. Large attachment moves to file link; telling this from the start cuts support load. When backup mailbox is deleted, legal archive may also go—retention period is company policy, technical scope is written in package.
If you want Google Workspace or Microsoft 365, DNS is still planned; license count and calendar/contact need select that model. "Just hosting mailbox" can be simpler and cheaper. Mixed model breaks reputation.
If domain is at another registrar, pointing MX to us is enough; you stay the owner. Domain registration, SSL, and email can be bundled in the same quote. Email down is as priority as site down.
