resenIA
resenIA
Smart review management for your reputation
Help center

Knowledge base

Practical guides for the core resenIA workflow.

Add and manage reviews

Create manual reviews, filter the inbox and keep track of replies from draft to publication.

  1. Open Reviews and use Add manually.
  2. Paste the public review, rating, author and platform.
  3. Generate a draft, edit it and approve or mark it as published.

Configure the AI context

Give resenIA the business context it needs before asking for consistent replies.

  1. Complete business name, type, tone and language.
  2. Add response guidelines and things to avoid.
  3. Use the preview to test how the profile changes the answer.

Understand AI analysis

The analysis page turns enough diagnosed reviews into trends, risks and suggested actions.

  1. Add or sync enough reviews for the analysis threshold.
  2. Review the executive summary, risk level and customer pulse.
  3. Prioritize suggested improvements based on impact and effort.

Train adaptive learning

Corrections, approvals and feedback become reusable guidance for future drafts.

  1. Generate responses from real reviews.
  2. Edit drafts before approving them when needed.
  3. Use positive and negative feedback to reinforce what works.

Recommended first session

A short path to understand resenIA without configuring everything at once.

20 minute setup
1. Define the basics

Add business name, category, tone and preferred language so the first drafts already have a clear personality.

2. Add real reviews

Use two or three recent reviews with different ratings to see how resenIA adapts the response strategy.

3. Edit before approving

Treat AI output as a draft. Adjust facts, promises and tone before marking the reply as approved.

4. Read the signals

Once there is enough activity, use Analysis and Learning to understand patterns and improve future replies.

Daily review workflow

Use statuses to avoid losing track of what still needs a human decision.

  • New means the review has not been answered yet.
  • Needs approval means there is a draft that should be reviewed.
  • Approved or published means the response is ready or already used externally.
  • Ignored is useful for duplicates, spam or reviews that should not receive a reply.

Response quality checklist

Before publishing, confirm that the reply is useful, specific and safe for the brand.

  • Mention the concrete issue or praise from the review.
  • Do not promise refunds, compensation or operational changes unless they are approved.
  • Avoid defensive language, especially on negative reviews.
  • Keep sensitive customer details out of public replies.

Handling risky reviews

Some reviews need extra care because they mention legal, health, safety or reputation-sensitive issues.

  • Slow down and verify the facts internally before publishing.
  • Acknowledge the concern without admitting facts that have not been checked.
  • Move sensitive resolution details to a private support channel.
  • Use human review for cases involving threats, discrimination, personal data or legal claims.
Configuration

What to write in the response profile

The profile is not a marketing brochure. It should give the AI practical rules, facts and boundaries it can reuse.

Good inputs

Opening hours, service area, usual tone, escalation policy, refund boundaries and frequent customer concerns.

Weak inputs

Vague instructions like be nice, sound professional or answer quickly without explaining what that means for the business.

Example guideline

For negative reviews, apologize for the experience, mention the specific issue, invite the customer to contact the manager by email, and avoid offering compensation in public.

Using analysis as a business tool

Analysis is most useful when it becomes part of weekly operations, not only a dashboard to read once.

  • Review the customer pulse to see whether sentiment is improving or worsening.
  • Use recurring topics to separate isolated complaints from operational patterns.
  • Treat suggested actions as a prioritization aid, then confirm them with business context.
  • Compare new reviews after a change to see whether the issue is disappearing.

Making learning improve faster

The system learns best from clear human decisions repeated over real examples.

  • Edit drafts instead of replacing them completely when possible.
  • Use negative feedback when the tone, facts or structure were wrong.
  • Approve good replies so the system can identify successful patterns.
  • Update the explicit profile when the same correction appears several times.

Troubleshooting

Replies feel generic

Add more concrete guidelines, business facts, things to avoid and examples of the tone you expect.

Tone feels wrong

Change the default tone, add one or two style rules, and mark bad drafts with feedback so learning has a signal.

Analysis is not ready

Add more reviews. Analysis needs enough diagnosed material before it can produce reliable patterns.

I cannot see an option

The interface only shows the flows active for your account. If you need help, check the FAQs or contact support.

New user recommendation

Start with configuration, add two or three real reviews, then revisit analysis and learning when there is enough signal.

Read FAQs