AI Agent Instructions

Procol-Llamadas is a B2B SaaS platform for commercial teams. It records phone calls from Android devices, transcribes them automatically, and provides a web dashboard for review, tagging, automation and team management.

1. Navigate to /register
2. Fill in:

   Field	HTML id	Type	Notes
   Organization name	orgName	text	Required. Your company or team name.
   Email	email	email	Required. Will be used for login.
   Password	password	password	Required. Minimum 8 characters.

3. Submit the form — on success you are redirected to /dashboard
4. If the email is already registered, the server returns an error message inline

1. Navigate to /login
2. Fill in:

   Field	HTML id	Type
   Email	email	email
   Password	password	password

3. Submit — session cookie is set automatically on success
4. Redirect target: /dashboard
5. On error: an inline message appears above the submit button

1. Navigate to /forgot-password
2. Enter the registered email address
3. Supabase sends a recovery link to that address
4. The link redirects to the platform where a new password can be set

All routes below redirect to /login if no valid session exists.

• Sessions are managed via Supabase SSR cookies — they persist across browser restarts.
• No token is exposed in the URL or localStorage.
• Unauthenticated requests to protected routes receive a 307 redirect to /login.
• The middleware runs on every request except: _next/static, _next/image, favicon.ico, brand-assets, api, terminos, privacidad, agents.

• The login and register pages are server-rendered — no need to wait for JS hydration before filling forms.
• Form submissions are standard HTML POSTs handled by Next.js Server Actions — they work without JavaScript enabled.
• After login, wait for navigation to /dashboard before interacting with authenticated content.
• Error messages appear as <p> elements with class text-destructive inside the form.
• All interactive form elements have stable id attributes (see tables above).
• The dashboard uses dynamic server rendering — content is always fresh, no stale cache to worry about.

• There is no public REST API documented yet. All data mutations go through Server Actions.
• Call recordings are stored in Supabase Storage — direct URLs require a valid session.
• Rate limiting is enforced by Supabase Auth on login attempts.
• The Android app handles call recording — the web platform is view/manage only.

If you are building an integration or need API access, contact: proyectoscolsas@gmail.com