Requirements elicitation

This page contains the results of the requirements elicitation process.

Requirements Brainstorming

Capturing incoming email from contacts and leads into Salesforce, including cases
Saving outgoing email to contacts and leads into Salesforce, including cases
Saving already-sent email into Salesforce if not already there, such as from Sent Items
View and edit Salesforce.com contacts and leads in the address book
Using email templates from Salesforce.com in new messages
Creating a new case from an incoming message
Incoming mail rules that route mail to Salesforce (needs more elaboration)
Ability to see email folders in Salesforce.com under a Thunderbird account (needs more elaboration)
Ability to send email to contact groups and dynamic queries that return contacts/leads (needs more elaboration)
More brainstorming needed...

Below are the features gathered from IdeaExchange. These will be refined and consolidated soon.. The original discussion exists on IdeaExchange.

Allow users to communicate via the familiar Thunderbird interface
Embed Salesforce right into Thunderbird (?)
Capture critical customer email in Salesforce with a single click in Thunderbird
Ensure no customer service issue falls through the cracks
Reduce email clutter by allowing users to log only necessary emails
Syncing of email in T-bird's Sent folder, but only if recipient's email address is in Salesforce's contact database.
Synchronization of all Sent email in Salesforce to T-bird's Sent folder (no more bcc:)
Must work with POP and IMAP servers
Syncing a subset of T-bird's address book with Salesforce (don't want all of T-bird's address book in Salesforce)
Upload sent / received / outgoing emails to salesforce
Create cases directly from TB
Address book syncing a bonus
Add emails to SFC directly from the mail app
Calendar sync

The detailed requirements are listed on another page. The high-level requirements are listed below: