Agents & intermediaries — mobile issuance, in-field signing
Native app for agents, sub-agents and collaborators: in-field issuance, customer signing on touchscreen, push notifications, biometric 2FA access.
The 4 headaches of the field agent
Notepad + re-typing
Customer visit: data on paper, then return to office to type everything on PC, issue policy, print. Time lost: 1-2 hours.
Customer signing in two steps
Issuance on PC, paper print, return to customer for signing, scanning, archival. Paperless workflow? Never happens.
Sub-agents sending policies via WhatsApp
Photos of paper forms via WhatsApp, data lost in chats, duplicate customer master data, transcription errors.
Real-time push? Never existed
Claim reported by my insured customer: I find out 2 days later from the insurer. Policy pending signature: I learn by email the term expired.
The office in your pocket, the policy in 60 seconds
| In-field activity | Status quo | With NewPicass 14.Net |
|---|---|---|
| On-site policy issuance | 1-2 hours (notepad + office PC) | 60-90 seconds on tablet |
| Customer signing | Print + return visit | Directly on touchscreen (FEA) |
| Customer event notification | Email or phone 1-2 days later | Real-time push even with app closed |
| Sub-agent coordination | WhatsApp + Excel | Multi-user app with RBAC permissions |
| Secure access | Sticky-note password | Face ID / Touch ID + remote wipe |
| Offline mode | App not working | Consultation + drafts with deferred sync |
How the platform fits your role
Intermediary compliance
On an agent / sub-agent in the field
Frequently asked questions from intermediaries
Difference between broker, agent and intermediary?
Broker = independent intermediary acting for the customer, mandated by insurers. Agent = exclusive (single-mandate) or multi-mandate intermediary, acting for one or more delegating insurers. Intermediary is the umbrella term covering both, plus sub-agents, collaborators, producers. In IVASS they're registered in different sections of the RUI (A for agents, B for brokers, E for collaborators).
Is the mobile app for intermediaries or also for brokers?
Both. The mobile app is designed for anyone operating in the field: agents visiting customers, sub-agents, brokers signing policies on-site, collaborators presenting quotes. Multi-insurer native: a sub-agent working with 3 different insurers switches between portfolios from the app menu.
Can I issue a policy directly on the customer's tablet?
Yes, it's the main use case. Typical workflow: customer visit, data entry on tablet with auto-fill from ID document OCR, real-time premium computation, customer signs directly on the tablet screen (graphometric FEA signature), policy issued and active in 60-90 seconds. The signed PDF is available for email/PEC to the customer immediately.
How does offline mode work?
On iOS and Android, offline mode enables: consultation of policies issued in the last 90 days (configurable), search of already-registered customer master data, opening a policy draft with deferred sync on connection return. Operations requiring real-time validation (CIG on ANAC, AML screening, premium computation with live tariff) are blocked offline.
Is the app security adequate for insurance?
Yes. DORA art. 8 (secure access) compliance: email + password + 2FA TOTP/SMS login on first access, biometric unlock (Face ID / Touch ID / Android fingerprint) on subsequent sessions, 12-hour session expiry, remote wipe on loss, Apple MDM and Android Enterprise compliance for device management. End-to-end encryption.
Can I be an agent for one insurer and broker for other lines?
Yes if authorised by both RUI sections (A + B). The system handles the dual configuration: for some products you operate as a mandated agent (sees only the delegating insurers), for others as a broker (sees multi-insurer with comparative quotation). RBAC automatically differentiates what you can do in each role, separate audit log.
See NewPicass 14.Net as it would work for a intermediari
45 minutes with one of our engineers. We show you concretely how the platform fits the specific workflows of your role — not a generic product demo.