Customer support for high-value investors

Customer support for high-value investors

Self-serve FAQs, pre-routed tickets and RM-approved replies that halved first-response time.

Self-serve FAQs, pre-routed tickets and RM-approved replies that halved first-response time.

Golden retriever dog sitting near solar panels and camper
Golden retriever dog sitting near solar panels and camper
Property Share is a fractional commercial real estate platform with ₹2,000 Cr+ in assets, where investors value a personal connection with their relationship manager as much as the returns.

I designed its support system from 0 to 1: pre-routed tickets, tier-based response windows, and replies shaped by each investor's RM, with an AI phase for reply drafting and call prep. Investors used to wait almost a week for a first human reply; now they get one in under a day.

Problem at hand

Customer conversations lived across emails, phone calls, Slack messages, and spreadsheets. Without a unified workflow, ownership was unclear, responses were delayed, and communication was inconsistent.

Designing for three kinds of users

Every ticket passed through three groups, and none of them could see the full picture. Each one got its own view of the same system.
Icon
Investors

The front-facing side: they raise requests and see only their own tickets

Icon
Relationship manager

The bridge between investors and the internal team, answerable for all the actions

Icon
Internal team

Specialist teams who own the answer, and leadership who oversee the system

Icon
Investors

The front-facing side: they raise requests and see only their own tickets

Icon
Relationship manager

The bridge between investors and the internal team, answerable for all the actions

Icon
Internal team

Specialist teams who own the answer, and leadership who oversee the system

Navigating the mess

How support actually worked

I wanted to see the messy process as it really ran, not the version people described. I shadowed RM calls, spoke with specialist teams, and reviewed session recordings. Key finding from my sessions:
Investors help themselves first

They opened 3–4 FAQs before asking for help. The habit was right, the content wasn’t.

Clarity beats speed

Investors would wait for the right answer, as long as they knew when to expect it.

No one saw the full picture

RMs owned the relationship, specialists the answer, and leads the SLA, but every ticket passed through all three.

Design Principle

Build trust first, then optimise speed.

Before making anything faster, every investor had to know who had their request and when they’d hear back. Where the two conflicted, like RM approval adding time before a reply, trust won. Speed came from routing, and later from AI drafting in phase two.

Key decisions that shaped the system

Research showed investors would wait for the right answer if they knew when to expect it. These decisions put clarity and ownership first, then speed.

01

Route every request at creation

Each FAQ maps to the team that owns it, so a ticket reaches the right people in one step instead of three.

01

Route every request at creation

Each FAQ maps to the team that owns it, so a ticket reaches the right people in one step instead of three.

01

Route every request at creation

Each FAQ maps to the team that owns it, so a ticket reaches the right people in one step instead of three.

02

Measure first response, not resolution

Some requests take minutes and others wait for month-end, so the SLA tracks only what a team controls.

02

Measure first response, not resolution

Some requests take minutes and others wait for month-end, so the SLA tracks only what a team controls.

03

Escalation goes through the RM

Investors can’t escalate on their own. The RM decides what’s urgent, so tier priority holds.

03

Escalation goes through the RM

Investors can’t escalate on their own. The RM decides what’s urgent, so tier priority holds.

03

Escalation goes through the RM

Investors can’t escalate on their own. The RM decides what’s urgent, so tier priority holds.

04

RMs approve every reply

Specialists write the answer. The RM edits and sends it, so each reply comes from someone who knows the investor.

04

RMs approve every reply

Specialists write the answer. The RM edits and sends it, so each reply comes from someone who knows the investor.

04

RMs approve every reply

Specialists write the answer. The RM edits and sends it, so each reply comes from someone who knows the investor.

Time-to-First-Response

0

.

0

%

Faster replies, from 46.2 to 20.8 hrs after launch

Time-to-First-Response

0

.

0

%

Faster replies, from 46.2 to 20.8 hrs after launch

Self-service

0

.

0

%

Increase in FAQ views over the first 6 weeks after launch

Self-service

0

.

0

%

Increase in FAQ views over the first 6 weeks after launch

Support Volume

0

.

0

%

Fewer requests per investor than the previous listing

Support Volume

0

.

0

%

Fewer requests per investor than the previous listing

Pull up a chair.
The kettle’s always on.

Most of my best design calls started as a chat over chai. Building something tricky? Bring the problem, I'll bring the chai. Or just pick a side below and say hi.

PERSONNEL 01

back

back

MY TOOLS

Figma · Framer · Notion

back

back

back

back

before we work together

• I'll ask "who's this for?" a lot

• I'd rather show than tell. I'll build it in code and send you a link.

• Teaching made me a better designer.

• A little OCD, about life in general.

• Chai first, critique second.

FILE NO. 04453

*************

everything you need to know before we work together. I'm organised by nature, intentional by design

I'm Samiksha Jain, a product designer in the US.

My expertise spans fintech, enterprise SaaS, internal tools and AI products.

• Thinking in Systems by Donella Meadows • Before the Coffee Gets Cold by Toshikazu Kawaguchi

CLOSE FOLDER

ABOUT ME

personal file on the designer behind the work.

Samiksha Jain

Product Designer

Say hi!

Ideal weekend

Best Bagel in NYC

Pull up a chair.
The kettle’s always on.

Most of my best design calls started as a chat over chai. Building something tricky? Bring the problem, I'll bring the chai. Or just pick a side below and say hi.

Samiksha Jain

Product Designer

Say hi!

Ideal weekend

Pull up a chair.
The kettle’s always on.

Most of my best design calls started as a chat over chai. Building something tricky? Bring the problem, I'll bring the chai. Or just pick a side below and say hi.

Samiksha Jain

Product Designer

Say hi!

Ideal weekend

Best Bagel in NYC