Support for EML Contacts

The desktop application starts and communicates with a local companion engine on the same computer. The engine opens your project and performs the processing work.

If the application or engine does not start, note the error shown. Restart EML Contacts, then check the project status on Home. If processing was interrupted, inspect the saved project status and completed contact lists before retrying; a missing activity entry does not prove that work failed.

Once connected, use Settings → Diagnostics to refresh the diagnostic information. A support bundle requires a captured diagnostics snapshot; it cannot be created while the engine is disconnected.

On Import, choose an EML folder, an Outlook PST file, or an MBOX file or folder. These are local archive imports, not mailbox sign-ins.

Check that a project is open and ready before starting. After an import, check its result for imported, duplicate and failed message counts. Import, Run Extraction and Build Contact List are separate actions; importing alone does not create a completed contact list.

Ollama is separate third-party software for local inference. EML Contacts does not install or start Ollama, or download its models automatically.

Check the local Ollama status on Processing. If it is unreachable, check that your separately managed Ollama service is running. If the configured model is missing, install that model through Ollama, then refresh status.

Run Extraction requires the configured local Ollama service and model to be available. Ollama being unavailable does not make your project database inaccessible: with the local engine connected and a compatible project open, you can still review and export existing completed contact lists. An available model status is not a guarantee that inference will succeed.

Use Backup Project on Home to save a complete local project backup containing project data. Choose an appropriate local destination and look after this file as carefully as the project itself. A project backup is not a support bundle.

Wait for processing and review actions to finish before maintenance. Use Restore Backup as New Project to create a separate project database; the backup is left unchanged. An older restored project may still require an explicit upgrade before use.

In Export, select a completed contact list, choose CSV, XLSX or VCF, and choose a local destination for the file.

Check the review scope before exporting. All cleaned contacts includes rejected contacts; choose Exclude rejected contacts or Approved contacts only when that is what you need. Refresh the preview after changing your selection.

These are file exports. EML Contacts does not directly synchronise contacts with Outlook, Microsoft 365, Google Contacts or a CRM.

Open Settings → Diagnostics and choose Refresh Diagnostics while the engine is connected. The snapshot includes desktop and engine versions, compatibility and project database state, Ollama status and configured model, aggregate processing counts, and current-session job states and error codes.

Copy Diagnostics copies the same structured information used by the support bundle. Refresh after reconnecting so that the snapshot reflects the current state.

Email support@emlcontacts.com.

When asking for help, describe what you were trying to do, what happened and any error code shown. If the application will not start, record the visible error rather than trying to create a bundle. Review any screenshots for personal information before sharing them.

If appropriate, create and review a support bundle before attaching it. The bundle is not sent automatically.