Excel export for Community managers
Community problems arrive as direct messages and emails. A weekly table shows patterns before they become a crisis. This page lists the exact columns, an example row and the command that produces it.
Columns to keep
| Column | Why it matters |
|---|---|
member | Community username, not the real name. |
topic | The subject of the commitment or conversation. |
sentiment | Fixed three-value scale: negative / neutral / positive. |
action | What has to happen, in one sentence. |
date | Message date in ISO 8601; sortable and unambiguous across time zones. |
Example row
One real-shaped row from this role’s export:
| member | topic | sentiment | action | date |
|---|---|---|---|---|
| user_8821 | billing bug | negative | escalate | 2026-10-16 |
Export it in one command
python mail_to_excel.py \
--host imap.example.com --user you@example.com \
--days 31 --fields member,topic,sentiment,action,date \
--out community-manager.xlsx
The --fields option is what turns a raw dump into a report your role can use.
Provider notes
Discord and Telegram are not IMAP; import their exports separately and merge on username.
Two pitfalls that ruin the file
- Member identities are stored where they should not be — Keep usernames, not real names, and avoid copying message bodies.
- Sentiment is guessed inconsistently — Use a fixed 3-value scale (negative/neutral/positive) and define it once.
Next step
Step-by-step: export community manager email to Excel · all roles · ready script ($3)
FAQ
Can this track NPS?
It can collect the raw signals; NPS calculation belongs in the survey tool.
How do I avoid duplicates?
One row per conversation, keyed by the first message id.
Is there a ready script for this?
Yes — the Python script exports any IMAP mailbox with the fields listed above; it costs $3 and runs locally.
Related guides
- Export community manager email to ExcelStep-by-step with the same columns and command.
- All roles20 professions, one export method.