Create Portal / Account
General Client account workflow in Proplix
The General Client route in Proplix is the standard account-creation path used when a new relationship needs to enter the platform as a customer record without being forced into a landlord, tenant, supplier or other specialist account type. It is a flexible starting point, but it is not a weak one. In the verified current Proplix build, that same client account can sit alongside contacts, files, statements, estimates, invoices, payments, proposals, contracts, subscriptions, projects, tasks, support activity and appointments.
That makes the General Client page far more important than a simple “add customer” explanation. It is really the public explanation of how Proplix handles standard customer relationships inside one connected operating system. A client record is not only a name, phone number or email address. It is the place where commercial movement, account history, documents, follow-up activity and service delivery can stay much easier to understand.
This page is written around the verified current Proplix feature set already surfaced by the help audit. It is not generic CRM filler. The categories below explain the real native areas that matter around the General Client account and why they belong together inside one structured platform.
Why this page matters
A General Client account is the starting point for much more than contact storage
In many systems, a standard customer record is treated as a dead-end admin object. In Proplix, the stronger position is different. A General Client account can become the centre of a broader customer relationship where commercial activity, files, billing, agreements, tasks, support and scheduling all remain easier to follow in one place.
That is especially important for businesses that want a cleaner operational environment. Teams do better work when they do not have to rebuild the same customer story across disconnected modules. The more the client record carries naturally through the workflow, the more professional and more reliable the service model becomes.
General Client categories in the verified Proplix build
These pages divide the native General Client-related flow into clearer website categories, while staying grounded in the actual Proplix feature structure already verified through the current help centre audit.
01
Account & Contacts
The verified Proplix client record structure covers the core account profile, contact handling, relationship context, notes and reminders that sit around the customer record.
Open detailed page
02
Files, Statements & Vault
The verified Proplix help flow shows that client records can sit alongside files, attachments, statements and vault-style document visibility rather than leaving those items scattered elsewhere.
Open detailed page
03
Billing, Estimates & Payments
The verified Proplix build already includes real commercial flow across estimates, estimate requests, invoices and payments, and those are key parts of what a standard client account must support.
Open detailed page
04
Proposals, Contracts & Subscriptions
The verified Proplix help structure confirms that proposals, contracts and subscriptions are native parts of the broader client-facing commercial flow.
Open detailed page
05
Projects, Tasks & Support
The audited Proplix help centre confirms that projects, tasks and support are native operational areas, and they become more useful when tied back to the right client record.
Open detailed page
06
Appointments & Client Engagement
The verified Proplix build includes a live appointments flow, public booking visibility and appointment history, which are all relevant to how a general client relationship is managed over time.
Open detailed page
What the General Client route actually covers
The blocks below summarise the real native areas that make a General Client account useful inside Proplix. Each block links to a fuller explanation page built from the same verified feature flow.
01
Account & Contacts
When a team creates a General Client account in Proplix, the first layer that matters is the account and contact structure. This is where the business establishes who the customer is, how the relationship should be understood, who the main points of contact are and what context the wider team needs in order to work properly.
- General Client account profile and core business/customer details.
- Primary and additional contact handling linked to the client record.
- Cleaner relationship structure for day-to-day staff use.
- Notes, reminders and follow-up context around the customer record.
02
Files, Statements & Vault
A strong general client workflow is not only about names and contacts. It is also about keeping the account connected to the documents and record outputs that the business uses every day. In the verified Proplix help structure, that includes client files, attachments, statements and vault entries.
- Client-linked files and attachments held closer to the account record.
- Statement visibility around the customer relationship.
- Vault-style record handling within the wider Proplix environment.
- Cleaner document access for staff working inside the same account context.
03
Billing, Estimates & Payments
A General Client account becomes commercially useful when it can carry estimate activity, invoice flow and payment visibility without the team needing to recreate the relationship elsewhere. In the verified Proplix build, those billing-related capabilities already exist through the native estimates, invoices and payments structure surfaced by the help audit.
- Estimates and estimate requests linked to the customer relationship.
- Invoices and recurring invoice behaviour in the broader Proplix billing flow.
- Payments and payment history linked back to the client context.
- Customer billing visibility that stays closer to the relationship record.
04
Proposals, Contracts & Subscriptions
Not every customer relationship moves straight from account creation into invoicing. Often there is a more deliberate commercial journey first: a proposal, a formal contract, a subscription structure or a longer-term agreement. In Proplix, those areas already exist as verified native workflow sections, which makes them highly relevant to the General Client account story.
- Proposal handling around comments, acceptance flow and conversion context.
- Contract management and longer-term agreement visibility.
- Subscription-style continuity where the relationship has recurring commercial value.
- A clearer link between customer record, commercial offer and ongoing agreement.
05
Projects, Tasks & Support
Once a relationship becomes active, the business usually needs more than just billing and documents. It needs delivery. That can mean projects, internal tasks, service follow-through, support tickets or a broader record of work in progress. In the verified Proplix build, those operational layers already exist and can be understood as part of the wider General Client journey.
- Project workflow around milestones, files, discussions and linked activity.
- Task handling for internal delivery and follow-through.
- Support or ticket-led service movement around the client relationship.
- Cleaner visibility of what the team is doing for the customer.
06
Appointments & Client Engagement
A customer relationship often needs scheduling and communication, not only records and billing. In the audited Proplix build, appointments are a real part of the platform, including booking flow, client-facing scheduling behaviour, history and reporting. That makes them a natural extension of the General Client account story.
- Appointments workflow in the verified Proplix build.
- Public booking and client-side appointment interaction.
- Appointment history and reporting context.
- A more connected customer engagement layer around the account.
Exact native feature breakdown by category
This section makes the feature scope explicit. It is designed to help buyers and users understand that the General Client route in Proplix can support a much broader relationship lifecycle than a basic address-book style record.
Account & Contacts
- General Client account profile and core business/customer details.
- Primary and additional contact handling linked to the client record.
- Cleaner relationship structure for day-to-day staff use.
- Notes, reminders and follow-up context around the customer record.
- A stable base for future billing, documents, support and commercial activity.
Files, Statements & Vault
- Client-linked files and attachments held closer to the account record.
- Statement visibility around the customer relationship.
- Vault-style record handling within the wider Proplix environment.
- Cleaner document access for staff working inside the same account context.
- A more reliable history around what was stored, shared or referenced for the client.
Billing, Estimates & Payments
- Estimates and estimate requests linked to the customer relationship.
- Invoices and recurring invoice behaviour in the broader Proplix billing flow.
- Payments and payment history linked back to the client context.
- Customer billing visibility that stays closer to the relationship record.
- A cleaner commercial journey from early commercial discussion through live payment handling.
Proposals, Contracts & Subscriptions
- Proposal handling around comments, acceptance flow and conversion context.
- Contract management and longer-term agreement visibility.
- Subscription-style continuity where the relationship has recurring commercial value.
- A clearer link between customer record, commercial offer and ongoing agreement.
- Better continuity between pre-sale discussion and live account management.
Projects, Tasks & Support
- Project workflow around milestones, files, discussions and linked activity.
- Task handling for internal delivery and follow-through.
- Support or ticket-led service movement around the client relationship.
- Cleaner visibility of what the team is doing for the customer.
- A stronger bridge between account creation and live service delivery.
Appointments & Client Engagement
- Appointments workflow in the verified Proplix build.
- Public booking and client-side appointment interaction.
- Appointment history and reporting context.
- A more connected customer engagement layer around the account.
- Cleaner continuity between contact management and live scheduling activity.
See how General Client accounts can fit into your Proplix workflow
If your business needs a cleaner standard client structure that can support documents, billing, agreements, projects, support and appointments without breaking the account history apart, Proplix is designed to give you that connected working model.
A controlled view for each participant
How General Client fits into dependable property operations
The strongest starting point is the work people actually complete, including the exceptions that rarely appear in a process diagram. A portal should not be a second disconnected database. It should present an authorised view of the same property operation so that a request, document, decision or update remains connected with the internal record that staff use.
Give each role enough context to act
Different participants have different reasons for signing in. A tenant may report a repair, a landlord may review portfolio activity, a supplier may update a job and a staff member may need wider operational context. Permissions must follow those responsibilities precisely. For General Client, that means access should follow an evidenced business need and change when responsibility changes.
Keep the reason beside the action
Good portal workflow confirms what was submitted, who now owns it and what the participant should expect next. Internal teams should receive enough context to act without asking the user to repeat information already supplied through the portal. This makes the General Client record more useful during absence, escalation, service review or a later audit.
Design for the case that does not fit
Property work includes incomplete forms, late evidence, changed instructions, unavailable suppliers and circumstances requiring discretion. The system should expose those exceptions, preserve notes and direct them to an authorised person instead of silently forcing a misleading “complete” status.
Configure from representative work
Before launch, test ordinary and awkward journeys with representative users, including missing evidence, incorrect selections, delegated access and closed cases. Clear labels, accessible forms and reliable failure messages matter as much as the visual design. Document what remains outside the system as well, so teams understand the boundary between Proplix, connected services and professional responsibility.
Measure whether the work is improving
Review successful task completion, repeat contact, abandoned journeys, response times and permission-related incidents. A portal is useful when it removes uncertainty while preserving human support for situations that do not fit the standard route. Review findings with the people completing General Client work, because a dashboard may not reveal the manual workaround being used beside it.
Keep guidance, permissions and records current
Ownership, legislation, services and internal policies change. Schedule periodic checks of access, templates, notifications, integrations and retained information. Record material changes and brief affected users so the configured workflow continues to reflect the organisation’s approved way of working.
Proplix supports structured workflow and evidence handling; it does not provide legal advice or remove the need for competent human review. Discuss your organisation, migration or integration requirements through the central secure enquiry route.
Discuss General Client requirements →What a well-run General Client process should make clearer
A member of staff opening the record should be able to understand its purpose, current status, owner and next meaningful action without first asking several colleagues for background. That does not mean every case follows an identical path. It means the agreed route is visible, departures are explained and supporting material remains beside the decision it informed. For General Client work, clarity is especially important when the case moves between teams or returns after a period of inactivity.
The day-to-day experience should also make uncertainty honest. Missing evidence, a disputed instruction or a review awaiting specialist input should be shown as an exception, not hidden behind a reassuring colour or forced completion state. Managers can then direct attention where it is useful, while staff retain a record of the checks already completed. This approach supports a more natural conversation with landlords, tenants, suppliers, clients and colleagues because updates come from a current operational record rather than a hurried reconstruction.
Good information design reduces unnecessary detail without removing useful context. Labels should use the language the organisation actually understands; permissions should reflect real responsibilities; and notifications should be reserved for events that require awareness or action. When every minor system event generates an alert, important work becomes harder to see. A considered General Client configuration therefore balances automation with judgement and gives authorised users a practical way to explain, reassign or escalate unusual work.
Implementation is not finished when data has been imported or users have received a login. Teams need time to test live examples, compare the configured route with policy, correct weak source information and agree how questions will be handled after launch. Early reviews should look for duplicated entry, private spreadsheets, unclear ownership and steps that users routinely bypass. Those observations are useful evidence: they show where the design, training or operating decision still needs attention rather than placing all responsibility on the person using the system.
Over time, the organisation should be able to show whether General Client work is becoming easier to complete and easier to explain. Useful evidence may include fewer avoidable chasers, faster retrieval, more complete handovers, better-quality submissions and a smaller backlog of unresolved exceptions. Measures should be read alongside real cases and user feedback. Proplix provides the connected workspace for that improvement, while accountable people remain responsible for policy, professional decisions and the service ultimately delivered.