ChatLik AI image vision — chat and post

ChatLik AI image understanding is typically enabled with Receive Images in Chat in preferences: the model then receives and analyses customer images (Vision path such as GPT-4o) at higher token cost. Related toggles cover including post images when replying to comments, with Vision warnings.

Before you start

1. Confirm your plan/model supports Vision and credits can cover images.
2. Open ChatLik AI Preferences and select the Page.
3. Prepare clear product photos for testing (no real customer PII).

Enable image receive

1. Turn on Receive Images in Chat.
2. Read the hint: analysis uses GPT-4o Vision at higher cost.
3. For comment replies with post images, review Include Post Image and its requirement that post text is enabled.
4. Save settings.

Test in Playground

1. Open AI Playground on the same Page.
2. Send a product image with a question (“Is this size available?” / “What’s the price?”).
3. If colour/model is wrong, improve AI Keywords and product description, or instructions.
4. Watch credit usage after image sessions.

After setup and verification

1. Document for the team: selected Page, who owns review, and when Playground was last tested.
2. Review day-one live replies, any error logs, and unexpected credit usage.
3. If price, policy, or hours change the same week, re-run the critical scenarios before trusting automation.
4. Keep a clear human escalation path when automation fails — never leave the customer without a fallback.

Ongoing quality control

1. Assign one owner to review this screen weekly so responsibility is not diffused.
2. On repeating customer complaints, reopen related settings and compare them with Business Profile and FAQ.
3. Log pause/edit decisions with a date so the next teammate knows what changed and why.
4. Do not treat setup as finished after the first save — review it with every new offer or season.

Practical tips

• Use clear photos on simple backgrounds while tuning.
• Do not rely on Vision alone for price — catalog is source of truth.
• Temporarily disable if credits are critically low.
• Recheck permissions if Save/Refresh buttons disappear after a role change.

Common mistakes

• Enabling Vision on an unsupported model/plan.
• Testing real customer invoice photos in a shared workspace.
• Ignoring credit spikes after image-heavy campaigns.
• Treating Save alone as success without a realistic customer scenario test.

Related: Playground · Products · Credits.

Next step

Try ChatLik via sign up or compare plans.