Email & Shared Inboxes

GigRoot handles email through shared inboxes. You forward an address such as [email protected] or [email protected] to GigRoot; mail arrives in the team's inbox, is filed onto the right lead, deal, ticket or candidate, and replies go out from that same address.

• Your own addresses — clients see replies from your domain, not from GigRoot.
• Filed automatically — mail links to the deal or lead it belongs to.
• AI triage — support mail opens tickets only for real issues; resumes become candidates.
• One composer everywhere — rich text, attachments, Cc/Bcc, AI drafting and your signature.

1. 1
   Add the inbox

   In Settings → Shared inboxes (under Integrations & AI), the owner or a manager chooses Add inbox and enters the address, the name clients see, and what its mail is for.
2. 2
   Forward the address to GigRoot

   Each inbox card shows Forward … to with a private routing address. Set up forwarding at your mail provider — the card has instructions for Gmail / Google Workspace, Outlook / Microsoft 365 and Hostinger / cPanel. If Gmail sends a forwarding confirmation, its code appears on the card. New address replaces the routing address if it ever leaks.
3. 3
   Enable sending

   Replies go out through Brevo. Add your own Brevo key and authorise your domain in Settings → Integrations → Brevo, or GigRoot sends on its own Brevo account. The card shows whether replies can go out, with Check with Brevo to test.

By default the whole team can read and reply; untick it to choose specific members. Owners and managers always have access. The card shows who it is shared with and when the last mail arrived.

• Sales & clients — mail files onto the lead, deal or contact it comes from.
• Support tickets — a genuine issue opens a ticket. AI decides which of your open projects it is about (or uses the inbox's default project), otherwise the ticket is left unassigned. A reply continues the same ticket and reopens it if it was closed.
• HR / recruiting — a job application with a resume adds a candidate in People (one per email address, résumé attached).
• General — mail is kept in the inbox for the team without being filed anywhere.

Mail lives in Communications. The navigation panel has Received, Sent and All mail; Needs reply when AI thinks mail is waiting on you; Spam when there is any; and one row per mailbox with its unread count. Filter the list by Linked or Unlinked.

• The reader shows From, To and Cc (and Bcc on your own sent mail), attachments with download, and images inside the message.
• Reply (or Follow up on sent mail), Reply all, Forward with its attachments, and Mark unread. Opening a message marks it read for the whole mailbox.
• Each message is badged with its Deal, Lead or ticket. Mail from someone unknown gets Create lead.
• Linking prefers the deal: a message joins the deal it was sent from, then a deal matching the client's address or company domain, and only then a lead. Your own team's addresses and free-mail domains never match.
• Only the agency owner can delete shared-inbox mail.

Search mail from the global search in the header — results include an Email group matching subject, sender and preview.

The same composer is used in the inbox, on leads and deals, and on tickets: choose the shared inbox to send From, add Cc and Bcc, write with the full rich-text toolbar (pasted Markdown keeps its formatting), Attach files (up to 15), or use Draft with AI. Mail sent from a lead or deal is linked to it and shows Linked on its timeline.

Set yours in Settings → Email signature. Pick a design — Classic, Stacked, Card, Compact or Minimal — or Write my own. The Modify panel starts from your profile and the company letterhead:

• name, title, company, email, phone, mobile / WhatsApp, website and address;
• the company logo (upload or use the company's), its size, and a colour;
• social links for LinkedIn, Instagram, Facebook, X and YouTube, shown as icons or text;
• an optional button and disclaimer.

With Add my signature automatically on, the composer adds it under your message (above the quoted text on replies), and you can remove it from a single email. Copy signature copies it for Gmail or Outlook too.

Tickets from a support inbox — and ones you raise by hand — are in the Tickets module, with views for untriaged, in progress, assigned to me, resolved and all tickets. Each ticket shows its client, project, email thread and SLA.

1. 1
   Assign

   Assign & create deliverable gives the ticket to someone and creates a resolution deliverable due within the SLA — 24 hours for critical, 48 for normal, 72 for low. The assignee is notified and the client is emailed that work has started.
2. 2
   Reply

   Reply from the ticket's Email thread; the client's answers thread back onto the same ticket.
3. 3
   Resolve

   Mark resolved & email client closes the loop. A later reply from the client reopens it.