Forwarding client emails to a project
Each project can have its own intake address. Learn who can forward to it, the checks every email passes, and what happens to emails that are not accepted.
When a client’s request arrives by email, you can forward it to the project’s intake address instead of pasting it. The email becomes a request on that project and is analysed against the confirmed scope.
Find the project’s intake address
- Open the project and choose Settings.
- Choose Email intake.
- The address is shown under Intake address. Select Copy to copy it.
Owners and Delivery leads can see the address. Viewers cannot.
A project has no address until an owner creates one. If you see This project has no intake address, an owner can select Create address on the same screen. The sample project never has one.
Forward an email
- In your email, forward the client’s message to the project’s intake address.
- Send it from your own work email: the one you sign in to Agreeably with, or an address an owner has allowed to forward.
Agreeably takes the client’s message from the forwarded email and makes it the request. Anything you wrote above it is kept as a context note called “Forwarder’s note”. Earlier messages in the thread are kept as a separate context note, so they are read as background rather than as new requests.
The original sender named in the forwarded email is shown as the sender, marked “(claimed)”. Agreeably cannot verify who the client really was, so it says so.
Who can forward
An email is accepted only when it comes from:
- the sign-in email of a member who has access to the project, or
- an address an owner has added under Settings, Email intake and that has been confirmed.
An owner adds an address, such as a shared projects inbox, with Add address. Agreeably emails that address a confirmation link, which lasts 7 days. Once confirmed it can forward into any project in the workspace. Resend link sends a fresh link; Remove takes the address off the list.
The sender check
Knowing the intake address is not enough to get an email in. Every forwarded email must also pass sender authentication.
In plain terms, your email provider signs each message it sends. These signatures are called SPF, DKIM and DMARC. Agreeably checks them to confirm the email really came from the address it claims to be from. A forged sender fails the check. If your own emails fail it, ask whoever runs your email domain to check its SPF, DKIM and DMARC settings.
Attachments
Attachments are listed on the request but are not analysed. Read them yourself, and if one matters, paste the relevant part as a context note on the request.
What you will see
- Accepted emails appear as requests on the project, marked Forwarded email.
- When the analysis finishes, the project’s delivery lead and the workspace’s owners get an email alert. Nothing is ever sent to the client.
- If your plan’s analyses for the period are used up, the request is held and analysed later, not dropped.
Emails that are not accepted
Agreeably never replies to a forwarded email, so the sender is not told it was refused. Instead, the Inbox shows a warning such as “1 forwarded email needs attention” for emails from the last 30 days.
Owners can open the project’s Intake log from Settings, Email intake, View intake log. It lists every email sent to the address, newest first, with who forwarded it, the original sender, the subject and any attachment names. Email bodies are never shown there.
Each email has one of these states:
- Accepted: it became a request.
- Quarantined: it failed a check. The reason is shown, for example it did not pass sender authentication, or it came from an address that is not allowed to forward.
- Failed: it could not be read, or it was larger than 2 MB. Paste the request instead.
- Released by an owner: an owner trusted a quarantined email and released it.
An owner can select Release on a quarantined email they trust. It then becomes a request. An email sent to an archived project cannot be released.
Emails are also quarantined once the workspace has received 30 in the last hour.
If the address leaks
An owner can select Issue new address. The old address stops working at once, and any email sent to it is quarantined. Turn off removes the address without issuing a new one.
Common questions
Can I forward the same email twice? Each forward is a separate email, so forwarding again creates a second request. If the same delivery reaches Agreeably twice from the mail service, only one request is created.
What if the project’s scope isn’t confirmed yet? The request is added and waits as Awaiting assessment. When the scope is confirmed, it is checked automatically, using one analysis.
Checked against the app on . Something out of date or unclear? Email hello@agreeably.io.