Feature

CRM built into your messaging inbox

Store customer profiles, custom fields, and tags right where conversations happen. No exporting, no syncing, no second tool. Workflows collect data automatically.

Start Free
Custom fields

Store any data type, per customer

Text & textarea

Free-form text fields. Single-line or multi-line for longer notes.

Date & datetime

Birthdays, last visit, follow-up dates. Used in workflow triggers (e.g., 'happy birthday').

Email, phone, URL

Pre-validated formats. Used for cross-channel identity linking and integrations.

File upload

Customer ID photos, signed forms, invoices. Stored securely.

Number & select

Numeric fields with validation. Select fields with predefined options.

Per-owner isolation

Your custom field schema is yours alone. Other accounts can't see your structure.

Workflow integration

Collect data automatically — no manual entry

Lead qualification

Ask budget, location, intent. Validate and store. Tag based on answers.

Onboarding

Collect name, preferences, special requests during first conversation.

Document collection

Ask for ID photo, prescription, signed agreement. File uploads handled in chat.

Identity & merging

One customer, one profile — across all channels

Auto-link by identifiers

Phone or email collected in workflows automatically links profiles across channels.

Manual merge

See two profiles that are the same person? Merge with one click. History combines.

Power features

Bulk operations and export

CSV export

Filter customers (by tag, date, field, channel), then export all data to CSV.

Bulk tagging

Tag 100s of customers at once. Use for campaigns or segmentation.

Bulk delete

GDPR-compliant bulk delete. Useful for cleanup and data retention policies.

FAQ

Common questions about Fiko CRM

No. Fiko is a 'mini CRM' built into your messaging platform — it stores customer profiles, custom fields, tags, and conversation history. It's not designed for sales pipelines, opportunity tracking, or marketing automation at the scale of Salesforce. For SMB messaging businesses, it's usually exactly enough.
Text, number, date, datetime, file upload, email, phone, URL, textarea (long text), and select (dropdown). Each field is per-business-owner so your custom schema doesn't conflict with anyone else's.
Yes. A Waiting node in a workflow asks the customer a question, validates the response (e.g., 'must be a valid email'), and stores it as a custom field. So you can build a quiz, a lead qualifier, or an onboarding flow without writing code.
Fiko links them into one profile. Two ways: automatically (when phone/email matches across channels) or manually (you merge two profiles into one with one click). The unified profile has all conversation history and shared custom fields.
Yes. Bulk export to CSV. Filter first (by tag, date, custom field, channel) then export. Useful for migrating data, generating reports, or feeding into external tools.
Yes. Tags can be applied manually or by workflows. Tags trigger workflow actions (add_tag trigger). They power segmentation for marketing campaigns and filtering in the inbox.
Yes. Each customer profile shows all stored custom fields with values, when they were set, and which workflow set them (if applicable). Useful for auditing data quality.

Stop losing customer data in chat history

Structure customer information into searchable, filterable fields — from day one.

Start Free Trial