Task Emails and Weekly Digest
min read - Updated on Oct 28, 2026Kimola emails your team about Tasks so that nobody has to keep the Tasks page open to know what changed. The assignee gets an email when a Task is assigned to them. The teammate who made the Task, its assignee and the teammates under Keep informed get an email when its status changes, when someone comments on it, and when Kimola measures whether customers noticed. Every Monday, each member with something to read gets a weekly digest of their open Tasks and of what their Tasks changed. All of these emails come from self@kimola.com.
Tasks are available in the Enterprise package.
Emails About a Task
An email about a Task goes to the people on it: the teammate who made it, its assignee and the teammates added under Keep informed (see Follow a Task). Kimola never emails the teammate who made the change, so you don't get an email about your own comment or your own status change. The email goes to the address of each teammate's Kimola account.
Every email shows what happened at the top, then the Task itself: its title, its priority, its due date when it has one, and the Space it was made in. A Task made from a finding also shows its evidence as it was when the Task was made, such as "1,240 pieces of feedback (8% of the space, NPS -32) when the task was made.", followed by the Task's description. Open the task in Kimola opens the Task's page.
Kimola never emails the teammate who made the change.
When a Task Is Assigned to You
When a teammate creates a Task for you, or hands an existing Task over to you, Kimola emails you. The subject is the Task's title, followed by "— from" and the name of the teammate who assigned it, and the email opens with "assigned you a task". If you assign a Task to yourself, no email is sent. See Create a Task.
When a Task's Status Changes
When someone moves a Task to another status, Kimola emails the people on it. The subject starts with the new status, then the Task's title and "— by" the name of the teammate who changed it.
In progress: someone clicked Start.
Done: someone clicked Mark done. For a Task made from feedback, this is also when the measurement starts.
Won't do: the team decided not to act on the Task.
Reopened: someone took a closed Task back to Open with Reopen.
The closing note asked for with Done and Won't do is not part of the email: open the Task to read it. See Manage Tasks.
A Task kept in Jira takes its status from the issue. When the issue's status changes in Jira, the people on the Task get the same email, with "— in Jira" at the end of the subject, and the email says which issue was marked with which Jira status (for example "CX-123 was marked Done in Jira"). See Send a Task to Jira.
When Someone Comments
When a teammate writes a comment on a Task, Kimola emails the people on it, except the teammate who wrote it. The subject is "New comment on", the Task's title, and the name of the teammate who wrote it. The email doesn't hold the comment itself: click Open the task in Kimola to read it and answer it on the Task's page.
When Kimola Measures the Task
Two and four weeks after a Task made from feedback is done, Kimola reads the same feedback again and tells whether customers noticed. The four-week result is the one Kimola emails, to the people on the Task. The subject starts with the result, followed by the Task's title.
Customers noticed: the finding's share of the feedback dropped clearly, or its NPS rose clearly.
No change yet: customers have not noticed a change yet.
It got worse: customers talk about the finding more than before.
Too little feedback to tell: there is too little feedback to tell yet.
The email also says what Kimola measured, for example "Four weeks after the task was done, its share of the feedback went from 12% to 7%", with the number of records before and after.
While an improvement holds, Kimola checks the Task again at eight and twelve weeks. If customers start talking about the finding as they did before the Task, the people on it get an email whose subject starts with "It came back:", saying that customers talk about it again and that you may want to open the Task again. On the Task's page, Open it again does that. See How Kimola Measures Task Impact.
When the Task follows a Jira issue, the four-week result is also written to the issue, so the team sees it where it plans its work.
A food delivery app has a Task, "Fix missing items in grocery orders", made from the Pain Points answer missing items. It was made by the customer experience lead, assigned to a product manager, and the head of operations is under Keep informed. When the product manager marks it done, the other two get an email with the subject "Done: Fix missing items in grocery orders — by" and the product manager's name. Four weeks later, all three get "Customers noticed: Fix missing items in grocery orders".
The Weekly Digest
Every Monday, Kimola sends each member one email with their week, which starts with "here is your week". It brings together the Tasks you have to do and the results of the Tasks you are part of, so you can plan the week without opening Kimola first.
The subject tells you how much is open, for example "Your week in Kimola: 3 open tasks, 1 overdue". When you have no open Tasks but one of your Tasks got a result, the subject is "Your week in Kimola: what your tasks changed". The digest has up to four parts, and a part with nothing in it is left out.
Overdue: your open Tasks whose due date has passed, each with the date it was due.
Due this week: your open Tasks due in the next seven days, each with its due date.
Also open: your other open Tasks, the ones due later or with no due date, each with its priority and its Space.
What your tasks changed: the results Kimola measured in the past week for the Tasks you made or are assigned to, each with its result: Customers noticed, No change yet, It got worse, Too little feedback to tell or It came back.
The first three parts list the open Tasks assigned to you, Tasks that are Open or In progress. Each part shows up to 10 Tasks, then how many more there are. Every Task title links to its page, and See your tasks in Kimola opens the Tasks page.
A member gets a digest only when there is something in it: at least one open Task assigned to them, or a result for one of their Tasks in the past week. Tasks you only follow under Keep informed don't appear in your digest.
The digest lists only the open Tasks assigned to you. To see how the Tasks you handed out are moving, open Created by me on the Tasks page.
Make Sure the Emails Reach You
Task emails and the weekly digest are sent from self@kimola.com. Some email services and company mail rules move messages from an address like this to a spam, junk or "other" folder, so a teammate may miss that a Task was assigned to them.
Add self@kimola.com to your safe senders or contacts. If your company filters email centrally, ask your IT team to allow the address for everyone who uses Kimola. If a teammate still doesn't get the emails, check that the email address of their Kimola account is the one they read.
Add self@kimola.com to your safe senders so that Task emails and the weekly digest land in your inbox.
The links in the emails open Kimola, so you may be asked to sign in first. If a Task was deleted after the email was sent, its page says "This task does not exist, or it was deleted." with See all tasks.