Cogryn User Handbook

Start with one business scenario. Give your weekly marketing work evidence, actions and a record of what happened.

Version: 2026-10-15 · For business owners, marketers, sales teams and agencies. Product button names remain in English so you can follow the interface in either handbook language.

Choose the problem you want to solve

The daily Signals workflow is “discover → verify → decide → follow up”. The weekly GEO workflow is “ask → read answers → find opportunities → change → measure again”. Use either product independently, or have your team manually turn recurring Signals questions into GEO questions. There is currently no automatic synchronization.

One Cogryn login does not grant access to every product. Company membership, Signals access and GEO access are managed separately. Your account and team setup determine plans, allowances and available channels.

Before you begin

• Define one business goal: service, customer type, service region, owner and the decision you want to make.
• Prepare your brand name, website, common aliases, main competitors and frequent customer questions.
• Assign a company administrator to manage monitoring scope and users to review results and act on them.
• Complete one scenario on the first day. Expand regions, platforms or questions after you have useful evidence.

The examples below explain workflows. They are not real customer data or promises of results.

Signals

Scenario 1: A mortgage adviser finds people considering refinancing

When: You serve New Zealand mortgage customers and want to find people comparing banks, approaching the end of a fixed rate or asking about refinancing conditions.

Prepare: Define your service region, eligible customer types, business template and platforms. Exclude regions you do not serve and obvious advertising phrases.

Steps: An administrator creates a goal in Monitoring goals. Reviewers filter Your signals by goal and source each day, starting with P1 / P2 and checking Review / Manual review as needed. Read the full post, scoring reasons and original source to check whether the author describes their own relevant need. After verification, choose Worth follow-up and record progress in Listening & follow-up.

Output: Verified discussions with actual stages such as awaiting follow-up, in conversation or meeting arranged.

Success: For each discussion, explain why it is relevant, where the original evidence is and who owns the next step. Volume and high scores do not establish real demand, permission to contact or a completed sale.

Scenario 2: A service team finds customer questions and brand feedback

When: Your team wants to understand recent questions, feedback that needs a response and topics to add to its FAQ.

Steps: An administrator adds business context and brand names to the goal. Open Listening & follow-up and choose Brand mention, Product question, Feedback or Bug report. Narrow results by region, language and text search. Read the original posts and save a feed with a clear purpose, such as brand feedback or service FAQs. Bookmark discussions for the team and export the current filtered results.

Output: A reusable topic feed and a list of feedback or questions backed by original posts.

Success: Choose a few verified questions each week and assign someone to update the FAQ or follow up on service. Categories and sentiment match text; people still need to interpret the context.

Scenario 3: A marketer studies competitor discussions

When: You want to understand common comparisons and pain points when people mention competitors, then decide which questions this week's content should answer.

Steps: An administrator configures competitor names and business context. In Listening & follow-up, select Competitor mention, narrow with text search and check whether the original post actually compares products. Save a topic feed and summarize recurring questions. One negative comment does not establish purchase intent.

Output: Content topics backed by discussions, such as which fees and conditions to compare before choosing a service.

Success: The team can explain its topic choices using real discussions. Brand and competitor monitoring share the existing collection allowance; coverage does not include every post on a platform.

Scenario 4: A manager establishes a daily follow-up routine

When: Several people review discussions and may duplicate work or forget the next step.

Steps: Agree on a Saved feed. Members check Daily brief, read original posts, select the actual stage in Progress and click Save progress. Conversations and meetings happen through your usual tools; update the record after they happen. Each week, compare the recorded stages with actual follow-up.

Output: Progress history and an export of the current filtered results.

Success: Important discussions have a clear stage and records reflect real actions. There is currently no automated outreach, automatic reply, CRM synchronization or automatic owner assignment by customer.

First use: From sign-in to your first human decision

1. Sign in through your Cogryn invitation and check that Company is correct. Recheck the goal after changing companies.
2. An administrator clicks New monitoring goal, selects a Business template and enters a Goal name.
3. Choose Services to monitor, Target customers, Regions, Languages and Social media sources. Start with a scope the team can review.
4. Enter Business context and optionally demand phrases, Exclude phrases, brands and competitors. Extra phrases affect collection scope; they do not directly change scoring rules. Unknown regions are not automatically treated as local.
5. Click Preview search scope and check it, then Save draft. Existing monitoring continues using the enabled version while the draft is saved.
6. After checking, click Enable saved scope. Follow the goal card's guidance if a platform or allowance is unavailable; repeated clicks do not activate an unconfigured service.
7. Check Latest successful source update and Next planned update. First activation schedules initial collection. Daily updates are scheduled for 06:00 New Zealand time; results appear after collection finishes. Pause/resume does not repeat the initial collection.
8. In Your signals, choose Post period, Monitoring goal, Social media source and Priority category. The period uses the post's publication date, not the most recent collection date.
9. Read the post. Use Read full post for long text, Why this score for evidence, then open the original source. Check the author, region, need and timing.
10. Choose Worth follow-up, Maybe or Not a fit, recording a reason when unsuitable. Reviewed items leave the pending queue; find discussions and progress records later in Listening & follow-up.

If ordinary members cannot see editing controls, ask the company administrator to change the goal. Personal filters change your view; they do not change company-wide collection scope.

Daily use: Allow 10–15 minutes

1. Check goal status and the latest successful update. If one platform fails, check whether others still have results.
2. Review unreviewed discussions in Your signals. Start with high priorities and check all priorities as needed. Manual review needs a person to assess it.
3. In Listening & follow-up, choose a Saved feed and check Daily brief for the past 24 hours, Bookmarks and actual follow-up stages.
4. Verify original evidence before deciding how to act on the platform or in your existing business tools.
5. Click Save progress after a real update. Export filtered results periodically for team review; an export is not automatic CRM synchronization.

Weekly review

Scores help order review. Human feedback does not immediately train production scoring. Do not teach “high score = permission to contact / guaranteed sale”.

GEO

Scenario 1: Check whether your brand appears in customers' AI questions

When: Customers use AI to compare services and you want to see brands, competitors and citations in answers to specific questions.

Steps: Create a brand space and confirm website, aliases, market and competitors. In Questions, add meaningful discovery, comparison and purchase questions. Import genuinely captured answers through Answers. Sample only when an available API channel and budget are configured. Use Overview for mention data within the same scope, then open individual Answers to verify responses and citations.

Output and success: Trace each metric to its question, channel, date, successful answer and original evidence. Keep API sampling and imports separate. There is currently no monitoring of real consumer AI webpages, so these metrics do not measure the probability that all AI users will see your brand.

Scenario 2: Decide which content to change this week

When: Competitors appear for a topic while your brand is absent, and your team needs to prioritize content work.

Steps: Inspect cited pages in Sources. In Actions, click Find opportunities and review each task's Evidence and Suggested steps. In Optimize, confirm brand facts, upload page text you have rights to use, review suggestions and export. After your team publishes externally, record the publication date and measure again using fixed questions and comparable windows.

Output and success: A traceable chain from answer evidence to content change, human review, implementation record and repeat measurement. Citations and brand appearances are observations, not proof of causation. Completing a task does not guarantee better recommendations.

Scenario 3: An agency delivers a report clients can discuss

When: You need to explain what you observed this week, what you recommend and what has been done.

Steps: Create a separate brand space per client. In Reports, fix dates, questions and channels before creating a snapshot. In Client delivery, configure report branding, client role and scope. Create an expiring report link that requires sign-in, or use the browser's Print / Save PDF. Your team delivers report and invitation links itself.

Output and success: A report with clear scope, answer evidence, next actions and responsibilities. Links are not anonymous public links, and invitations do not automatically send email. Recipients still need appropriate GEO membership and brand permissions.

Scenario 4: A content team compares sampling with website outcomes

When: You want to examine brand mentions, AI citations, website visits and business events.

Steps: In Results & assistant, use authorized website data snapshots or connect read-only GA4 when the service is enabled. Specify the snapshot time, website and key-event definitions. Read these results separately from answer evidence over the same period.

Output and success: Clearly distinguish citations, inferred crawler requests, actually recorded visits and customer-defined business events. Unconfigured data stays unknown; do not replace missing data with zero or describe correlated changes as proven revenue growth.

For detailed GEO controls, sampling definitions and repeat-measurement conditions, see User handbook inside GEO. Current operating records show that online model channels and GA4 have not been enabled; use your account's actual availability as the guide. Search research provides web research material, not AI answers or mention-rate data. If the page is empty, start by organizing brands, questions and sourced material for import.

Your first week

Repeat-measurement windows depend on actual publication and sample coverage. Comparable results are not guaranteed in the first week.

Common questions

I cannot see data

Signals: Check Company, enabled goal, latest successful update, Post period, source and priority. Try All priorities where needed. No recent matching discussions may be a valid result. The unavailable state means collection status cannot be confirmed; it does not mean zero demand.

GEO: Check organization, brand, dates, Mode, Channel and question version. The API view does not automatically show imports, and Search research does not populate Answers. Without successful answers, metrics should stay unknown.

I cannot save or enable a goal

Check your role and product permissions. Preview first, then save a draft. For a version conflict, refresh and recheck your edits. If allowances, platforms or budgets are unconfigured, ask your administrator to contact Cogryn. Repeated retries do not solve missing setup.

A score or category looks wrong

Check the original post and Why this score / Evidence. In Signals, record a Not a fit reason or leave it for human review. In GEO, check brand aliases, questions and sampling mode. Keep specific evidence for team review instead of reporting only a score screenshot.

Training video plan

Start with short task lessons. Each should explain one scenario and ask learners to deliver a checkable result.

Detailed recording outlines, script structure, exercises and maintenance rules are in the repository's customer training plan. These videos are planned and have not been recorded. Start with a 30-minute scenario workshop and adjust recording order based on actual user difficulties.