Generoy guide
One clear next step, with your team in control.Choose a paused Concierge profile to begin.
Generoy · customer control
Plan the inbound role.
Keep the decision visible.
Set the job, review each proposed system boundary and keep a visible human handoff. Generoy keeps the role brief, owner decision and review path in one place before any provider or channel is considered.
Checking protected Generoy access…
Pre-release workspace
Protected Generoy access is not open yet.
Public account creation, sign-in and customer workspace setup are not available in this pre-release build. No credential, role brief or business detail is sent from this page.
See how a role is reviewedLocal preview only · no payment, provider connection or external action.
Medium Business and higher
Generoy role planning starts with Medium Business.
Verified Medium Business, Large Business or Enterprise commercial access is required when the service is available. Billing is not connected in this release, so no card can be charged from this page.
Local preview only · no payment, provider connection or external action.
Workspace status
Generoy is temporarily unavailable.
We could not confirm access to this workspace. No configuration, payment, provider connection or external action was started.
Customer workspace
Good morning, there.
Loading your inbound-role review workspace.
Provider and external action remain off
Generoy guide
Rule-based guidance. No AI model is connected.What should we decide next?
Setup progress and requirements
Technical readiness details
Release preflight
Loading preflight status…Guidance only. No external action. Do not enter passwords, tokens or customer records.
Only reviewed profiles appear here.
You can pause before any external action.
Approved scope is not a live connection.
Review each requested purpose yourself.
Your roster
Choose a Concierge direction suited to the work.
Each starts paused as a staff-first inbound role direction. It does not connect a provider, number, recording, transcription or channel; any live setup needs separate evidence and automated setup verification.
Implementation brief
Give the Concierge facts, a boundary and a person to hand off to.
This brief scopes integration work. Do not enter passwords, tokens, customer records or card data.
Customer systems
Review each purpose before a connection exists.
A scope review only documents the intended integration. It never starts OAuth, saves a secret, reads data or sends an external request.
Business Audit
See what needs attention before adding a role.
Business Audit reviews only approved, connected sources after their data sync is complete. It marks gaps in coverage and suggests a focused role test; it does not connect a system, buy capacity or change a plan.
Readiness
Check the data boundary first.
Open this area to check audit access and source readiness.
A finding is an observation, not a verified cause. Review source records and business context before changing a role, process or budget.
Defendence · Security
Review the public boundary before considering deeper access.
Defendence is a separate security workflow, not Business Audit. This preview explains the proposed service boundary; it does not scan assets, monitor alerts or connect to your systems.
Planned · not active in this release No scan, alert feed, or Agent Factory request runs from this preview.
Standard subscription · proposed inclusion
Limited public-surface check
For exact public domains you control, after domain control is verified and you explicitly approve the scope. Only limited, unauthenticated HTTP(S) checks are proposed.
- Review public HTTPS/TLS configuration, security headers and narrowly scoped public exposure signals.
- Check only the approved public route list; do not guess hidden paths or follow cross-origin redirects.
- Stay within the approved host and request limits; stop if a redirect or shared service leaves scope.
- No credentials, exploitation, fuzzing, load tests, data extraction or changes are permitted in this profile.
Secret-like values are masked, never tested with a provider and never used to sign in.
Cadence, allowance and price are not approved yet. A public URL alone is not permission to test; third-party and shared-hosting assets are excluded by default.
Separate engagement · disabled
Deeper security assessment
Any authenticated, intrusive or exploit-style test requires separate written approval and verified authority for the exact assets and methods.
- Confirm the signer, exact targets, exclusions, allowed methods and time window.
- Set rate, impact and cost caps, data-use approval, active-test authorization and an emergency stop contact.
- Re-check scope, expiry and revocation before each attempt; no wildcard or redirect may expand scope.
No credentials, client logs or personal data are requested in this concept. A real engagement also needs a separate privacy, legal, capacity and runner readiness review.
Evidence and next steps
Separate a signal from a confirmed finding.
A future report must label each item as hypothesis, observed or validated, show scope and coverage, and distinguish “no signal found” from “not enough visibility”. An IP address or account is not proof of a person or intent.
Findings may become a draft remediation task or role proposal. The customer must approve the exact role, capability, asset scope and limit before a request goes to Agent Factory. No automatic role creation or activation.
Visible history
Every configuration step stays reviewable.
Activity records settings and scope decisions, not raw customer conversations or connected-system data.