Research guide

Best Delaware Statutory Trust Companies (2026): Comparing Complaint-Handling and Escalation Processes

By Sequoia ResearchPublished Read as Markdown

What Is This Article About?

This article compares where Delaware statutory trust (DST) companies direct concerns and open questions. It reviews two public pages checked on October 17, 2026, with separate scopes for investment and privacy concerns. The review had no private case files, response tests, or rates of successful outcomes. The examples show how to track an issue and assess a reply without turning a contact page into a rating. The goal is to show who should act and what remains open.

Table of Contents

Start With the Kind of Concern

A useful complaint process begins with a specific issue. “I am unhappy with the investment” may be true, but it leaves the recipient guessing about the problem. Is a payment different from the statement? Is a report missing? Was a fee described one way and charged another? Does the investor question how a recommendation was made?

Those questions may involve different entities and records. A sponsor's investor service team might explain a report's location. A brokerage firm might need to address a concern about its representative's statements. A privacy team might handle the use of personal information. One company name at the top of a website does not settle all those roles.

Start by stating the event, the evidence, and the requested action. A request to explain a calculation is different from a demand to correct a record. Both differ from an allegation that someone acted improperly. Use the category that fits the facts you know, and preserve uncertainty about facts you have not established.

Consider the fictional Juniper DST. Imogen has three concerns: a payment differs from her worksheet, an old mailing address remains in one file, and a sales statement appears to conflict with a later document. She could send one large message to every contact she knows. A clearer approach assigns each concern its own heading and asks who is responsible for each answer.

That structure does not reduce the seriousness of a concern. It makes the requested work visible. It also helps the reader tell whether a reply addresses the full issue or only one part of it. A corrected address does not, by itself, explain the payment or settle the sales statement.

What Two Public Company Pages Actually Disclose

The following is a limited comparison of current public access instructions. It is not a comparison of completed complaint investigations. The pages were checked on October 17, 2026. No message was sent, no account was accessed, and no response time was tested.

Public source Stated route or scope What remains unverified
Inland Investments, Important Disclosures Its social-media policy directs complaints away from LinkedIn, toward the financial advisor, with Investor Services as another contact Which entity would own a particular case, internal review levels, response commitments, and results
ExchangeRight, Privacy Policy The policy, effective May 27, 2026, names a Privacy Team for privacy questions or concerns An investment-complaint process, internal appeal steps, response commitments for a given request, and results

Inland's page lists Investor Services at 800.826.8228. The same page mentions complaints about continuing education. That passage should not be relabeled as a route for an investment dispute. No clear overall revision date was displayed for the page. These findings concern written instructions. Staff conduct was not tested. Inland Important Disclosures.

ExchangeRight names a team and lists mail, phone, and email contact details. Its stated subject is privacy. This does not establish who decides disputes about payments, sales advice, or offering terms. The date applies to the policy. It is not the date of a service test. ExchangeRight Privacy Policy.

The clearest difference in this small sample is the stated subject and routing role. One page addresses how to route complaints raised around a social-media channel. The other identifies a specialist privacy contact. Neither observation supports naming a winner. A full review of how firms escalate cases would need more evidence than these passages provide.

This limitation is useful before an investment as well as after one. Ask for the applicable written route for your concern and relationship. A reply can then fill a defined gap. Without that step, a broad “contact us” page can look more complete than it is, while a narrow specialist page can be judged against the wrong task.

Identify the Entity That Can Answer

Write the exact legal name beside each role in your record. If you only know a brand, label it as a brand until you confirm the entity. Keep the offering issuer separate from the sponsor, selling firm, adviser, and outside service company. Their work can overlap without making them interchangeable.

A practical question is: “Which entity is responsible for answering this part, and in what role?” The answer might identify a department rather than a person. That can be helpful if staff change. Record a verified contact route and any case reference, then keep the same issue description attached when the matter moves.

For Imogen, the payment question may need a statement and a payment record. The sales advice question may need the selling firm's messages and account files. The address issue may involve records held by a service firm. She should ask each party to confirm its role. A familiar logo does not settle that question.

There are two useful kinds of responsibility. One person can coordinate the case while another has authority to explain or correct a specific record. Ask who is doing each job. A coordinator should be able to say what is pending, even when an answer depends on another team.

Also distinguish responsibility for an answer from agreement with the investor. A firm can identify the right reviewer and still reach a conclusion the investor disputes. The quality of that conclusion depends on its reasoning and evidence. A named contact helps the process; it does not decide the merits.

When a message is forwarded, ask whether the new recipient has accepted responsibility. “I sent this to another team” describes an action by the sender. It does not establish that the next team received the full file, understood the question, or agreed to answer by a stated date. Keep the handoff open until those points are clear.

Separate Receipt, Investigation, and Resolution

A receipt notice shows that a message reached a system or person. It may contain a tracking number and a general promise to review. That is useful evidence of receipt. It is not evidence that the concern was investigated or that the claimed problem was fixed.

Use a small set of plain status labels. For example, record an issue as sent, receipt confirmed, assigned, evidence requested, answer received, disputed, or closed in your own file. These are organizing labels, not legal conclusions. Add a short reason whenever the status changes.

Suppose Imogen lists six issues in her fictional review. All six have receipt notices. Four have substantive answers, two remain unanswered, and one of the four answers is disputed. Receipt coverage is six out of six, or 100%. Answer coverage is four out of six, about 66.7%. Only three answers are currently accepted in her own record, or 50% of the six issues.

Calling that file “100% resolved” would collapse three different facts. Calling it “50% answered” would also be wrong. The denominator is the same, but the event being measured changes. Keep the labels beside the figures so another reader can reconstruct them.

Closure needs its own explanation. An investor may close a question because a correction was verified, because an explanation was accepted, or because the issue is being pursued elsewhere. Those reasons should not be merged into one success label. A closed administrative file can still contain a disputed substantive claim.

A later document can reopen an issue. Preserve the original answer and explain what changed. That gives the next reviewer a reason to revisit the matter without pretending that the earlier response never existed. It also prevents a resolved label from surviving after its supporting facts have changed.

Build a Clear Complaint Record

Keep one short issue statement at the front of the file. State what happened, when you learned about it, which source supports it, and what you want explained or corrected. Put the strongest relevant records behind that statement. A long attachment list is less useful if the reader cannot locate the disputed point.

Separate what you observed from what you infer. “The statement lists $1,500 and the bank record shows $1,350” is an observation if those records match the same period and owner. “The company withheld $150 improperly” adds a conclusion about cause and authority. That conclusion may require facts the first two records do not provide.

Use a chronology with dates and source locations. Include the date of the event, the date of the document, and the date you received it when they differ. A message sent on October 10 about a September payment should not turn the payment itself into an October event.

Keep copies of the records you rely on. The Financial Industry Regulatory Authority (FINRA) says to promptly question a broker about trades you do not understand or did not authorize. If the answer is not satisfactory, it directs you to the branch manager or compliance department. It also advises keeping copies of written records. That guidance concerns the brokerage relationship. It does not name the right team for every sponsor issue. FINRA File a Complaint.

Make the requested action concrete. Ask for the calculation, the applicable clause, the correct version of a document, or the reason a requested correction was declined. If you seek several actions, list them separately. This makes it harder for a reply to address an easy question while leaving the main one hidden.

Avoid filling a public form with full tax identifiers, bank details, or unrelated personal records. Ask for a secure route when the records contain sensitive data. A short source description may be enough to find the right team. Keep the full records for the authorized reviewer.

Check a Distribution Difference Before Naming Its Cause

Start a payment review by matching the records. Check the investor, interest, period, and meaning of each figure before subtracting numbers. A target annual rate, a declared monthly amount, and cash received are three separate measures. Their difference can raise a question without proving a specific cause.

Here is an original fictional case. Imogen invested $300,000 in Juniper. Her worksheet uses a 6% annual cash target and divides it evenly across twelve months. That creates a planning amount of $18,000 a year, or $1,500 a month. It is not a promise that every month's payment will equal that amount.

Her bank record shows $1,350 for the month under review. The arithmetic difference is $150. The received amount is 10% below the worksheet amount for that month. Those calculations do not establish whether the difference reflects timing, a changed rate, a partial period, an error, or another reason.

Fictional record Amount What it establishes in the example
Annual target calculation $18,000 $300,000 multiplied by 6%
Monthly worksheet amount $1,500 Annual planning amount divided by twelve
Bank receipt $1,350 Cash shown in the matched bank record
Unexplained difference $150 Worksheet amount less bank receipt

The next request should seek the actual calculation and its basis. Ask which period the payment covers, what amount was approved, and what record links that amount to the receipt. If an adjustment is claimed, ask how it was calculated and where it appears. Do not insert an assumed fee just to make the numbers balance.

If the following month brings $1,650, the two receipts total $3,000. That matches two months of the worksheet's planning amounts. It still does not prove why the first month differed or whether the second payment included a correction. A combined total can conceal a timing question that matters to the investor.

The Securities and Exchange Commission (SEC) describes several private-placement risks. Information can be limited, resale can be hard, and losses can be serious. Those risks remain even after a payment question is answered. Matching the records does not establish total return or the future ability to pay. SEC private-placement bulletin, updated September 21, 2026.

Compare Escalation Routes and Decision Authority

An escalation route explains what happens when the first answer leaves an issue open. It should identify a next role, the information needed, and how the prior record stays connected. A second inbox is not much help if the investor must start from scratch without a case reference.

Compare the route for the specific concern. A general service question may move to a specialist team. A disputed recommendation may need the selling firm's compliance review. A privacy request may follow its own process. Ask which route applies before treating all company contact choices as equivalent.

Before investing, a useful request is brief: “Where is the written route for a concern about this offering? Who reviews an unresolved response? How do I keep the same case reference?” You can assess the answer without making up a complaint or filing a test allegation.

Authority matters as much as access. Ask whether the next reviewer can explain the record, authorize a correction, or only relay a response. A team that can correct an address may have no role in deciding a dispute about a sales statement. Knowing that limit can prevent a series of unproductive handoffs.

In a fictional routing exercise, Imogen identifies four needed functions: receive the issue, obtain the records, make a substantive decision, and communicate the outcome. Three functions have named owners, while decision authority is unclear. That is three of four assignments documented, or 75% coverage. It is not a 75% chance of a fair result.

The missing function can matter more than the three present ones. A weighted score might hide that gap by rewarding a fast acknowledgment or a polished portal. Keep the gap in words: “No decision owner confirmed.” Then ask for that answer directly. The result is easier to act on than a broad service grade.

Measure Response Times Without Hiding Open Cases

Response speed needs a defined start and finish. Time from message submission to acknowledgment differs from time to a useful answer. Time to a correction differs again. Choose the event you intend to measure and keep unresolved matters visible beside the completed ones.

Imagine five fictional questions submitted on the same day. Four receive useful answers after one, two, three, and four elapsed calendar days. The fifth remains open after twenty days. Among the answered questions, the average is 2.5 days and the median is also 2.5 days. Those numbers say nothing about when the fifth will be answered.

Reporting only “average response: 2.5 days” hides the open case. A fuller description says that four of five received answers, gives the answered-case timing, and states that one remains open at day twenty. The 80% answer rate and the twenty-day age belong beside the timing result.

Do not record the open case as zero days. That would reduce the five-case average to two days and make a missing answer look fast. Do not record twenty days as a completed response time either. Twenty is the age of the open case at the cutoff, not the time of an answer that has not arrived.

A comparison also needs the same kinds of issues. A simple document-location request is not the same task as tracing a disputed payment across several records. One sample may contain routine questions while another has complex disputes. Their averages may reflect those different cases more than service quality.

Business-day claims need more detail. Confirm the time zone, daily cutoff, holiday calendar, and event that starts the clock. An email sent late on Friday may not share a start point with a Monday morning submission. Record the actual promise instead of translating “soon” into a firm deadline of your own.

Read Complaint Counts and Company Reviews Carefully

A review post is a statement by its author. It can identify an issue worth checking, but it does not establish every detail or represent all clients. Preserve the difference between an allegation, a company response, a settlement, and an established finding. None should be silently substituted for another.

Count people, issues, and messages separately. In a fictional search file, nine messages concern three underlying issues raised by two investors. Calling them nine complaints from nine investors would exaggerate both the event count and the number of people. The file should retain all nine messages while linking them to the three issues.

A repeated post can add context, but it is not automatically a new case. The reverse is also true: one long post can describe several separate concerns. Use a consistent rule for deciding what a case is, and state that rule before comparing counts across firms or years.

The population matters too. Suppose one invented service record has eight complaints among 400 relationships and another has twelve among 1,200. The simple rates are 2% and 1%. A raw-count ranking would put the second record behind the first, while the rate reverses that order. Neither measure settles severity, validity, reporting practices, or missing cases.

Even those rates need matching data. “Relationships” might mean active accounts, investors ever served, or completed sales. One investor can have several offerings. If those groups differ, the rates do not measure the same thing. Keep a missing denominator, the total used to calculate the rate, marked as unknown. Do not fill it with assets or a guessed client count.

FINRA says a written complaint appears in BrokerCheck only if it meets certain criteria. A missing entry does not prove that no concern was ever raised. The guidance also notes that a loss alone does not prove misconduct. FINRA Questions to Ask Before You File a Complaint.

Keep Regulatory Reporting Separate From Reply Deadlines

A firm's duty to report to a regulator does not itself promise a reply date for an investor. Before using a number, check who must act and what starts the duty. Note where the report goes and what the clock measures.

For example, FINRA Rule 4530 requires members to promptly report certain events. The outside limit is thirty calendar days after the member knows or should know of them. One category covers written customer allegations of theft, misappropriation of funds or securities, or forgery. Paragraph (d) has a separate duty. It calls for statistical and summary reports on written customer complaints after a calendar quarter. These duties concern member reports. They do not promise to resolve every client case within thirty days. FINRA Rule 4530.

The same distinction applies to a company's own wording. “We will acknowledge your request within two business days” addresses receipt. “We aim to provide an update within ten days” addresses an update and uses a different level of commitment. Neither sentence necessarily promises a final decision within that period.

In a comparison worksheet, copy the short relevant promise with its source and date, then describe its scope in your own words. Record whether it is a stated requirement, a service target, or a date proposed for your particular case. If the wording is unclear, ask rather than upgrading a target into a guarantee.

Keep legal deadlines outside this informal scoring exercise. An unresolved complaint may involve rights or filing periods that the company contact page does not explain. Do not assume that an acknowledgment, an internal review, or a request for more records pauses any other deadline. Get qualified advice about the facts and forum when needed.

Protect the Record When Information Changes

A complaint file often changes because new evidence arrives. Keep the old record and append the update with a date. Explain whether the new material corrects an earlier fact, adds a missing detail, or creates another conflict. Replacing the old document without a note can erase the reason the concern arose.

Suppose Imogen's original issue cites statement version one. The company later supplies version two with a revised amount. Her file should show both versions, the changed field, and the explanation offered. She can then check whether the new figure matches the payment record and whether any related question remains open.

Changes can affect more than one issue. In an invented four-issue file, three issues are marked accepted and one remains open. A later fee schedule changes the basis of two accepted answers. Reopening those two leaves one currently accepted issue and three open issues. The earlier 75% accepted figure becomes 25% at the new cutoff.

That change does not prove the earlier reviewer acted badly. It shows that the current conclusion depends on different evidence. Keeping both states is more honest than preserving a flattering completion percentage or deleting the original answers. State exactly why each issue reopened.

A handoff should preserve that history. Give the next reviewer a short current-status note, the earlier response, and the new evidence. Mark what needs a decision now. If the new reviewer only sees the original complaint, the revised concern can be missed; if the reviewer only sees the latest record, the disputed change can be hard to understand.

Avoid treating a file as tamper-proof merely because it is organized. A local spreadsheet or folder can still be edited. Keep original messages and documents where practical, with clear filenames and dates. The aim is a record another person can follow, not a claim that your filing method proves authenticity.

Use Outside Complaint Routes With the Right Scope

Internal routing and outside review serve different purposes. A firm's process may help explain or correct a record. A regulator may examine conduct within its authority. A route for seeking money or another remedy may require a separate process. Identify the outcome you seek instead of assuming one submission does everything.

The SEC's investor help page has separate forms. One is for complaints; the other is for questions or requests for information. That distinction can help readers describe their purpose. That does not mean the SEC reviewed a specific DST or accepted an allegation as true. It also does not promise to recover a loss. SEC Submit Questions and Complaints.

FINRA warns that even action against a firm does not assure payment or return of funds to an investor. It also warns about relying only on its investigation. Waiting too long may close other routes. Those limits make it important to understand the process and timing. A serious concern still needs attention. FINRA complaint questions and recovery limits.

Choose a route based on the entity and conduct involved. A privacy concern, a securities recommendation, and a dispute about an issuer's records may raise different questions. If the correct forum is unclear, seek help identifying it. A broad internet search can find several forms without showing which one fits the facts.

Keep the description factual in any route. State what you know, identify supporting records, and label estimates or assumptions. If you later learn a figure was wrong, correct it and preserve the explanation. A precise record helps a reviewer assess the issue without requiring you to prove every legal element in the opening message.

Compare the Evidence Without an Arbitrary Score

The useful output of this review is a set of supported observations and open questions. For each company, record the source, the concern it covers, the named receiving role, any next review level, and the limits of what was checked. Add the date you checked the page and any stated effective date separately.

Use plain findings such as “initial route identified,” “scope limited to privacy,” or “next reviewer not confirmed in this source.” Avoid turning those findings into stars. The existence of a route is evidence about access. It does not measure the fairness of a decision, the skill of an investigator, or the chance of recovery.

If a company supplies more detail, update only the findings that the new evidence supports. A written escalation policy might establish a next role and an expected update step. It would not, on its own, establish that every case follows that policy. Actual service records would require their own defined population, dates, privacy controls, and review method.

Before relying on a comparison, ask whether another reader could reproduce it. Can that reader find the cited passage, see the same issue category, and understand why a field remains unknown? Can the reader distinguish a public observation from a fictional teaching example? Those checks make the research useful without pretending it is a rating agency report.

For someone searching for the best DST companies, complaint handling is one part of a wider review. Clear responsibilities can reduce confusion when something goes wrong. They cannot repair a weak investment thesis or remove the risks of the underlying property. Keep service evidence beside, rather than in place of, the offering's financial and legal review.

FAQ

Does a Published Complaint Route Prove Good Service?

No. It shows how the company says a concern can be raised within the stated scope. Good service would require evidence about what happened after receipt. Check the assigned role, the quality of the answer, the source record, and any correction. This article did not inspect private case outcomes for the named companies.

Can I Compare a Privacy Contact With an Investor Service Team?

You can compare the clarity of their stated roles, but their functions differ. A privacy contact may address personal information while an investor service team may help with reports or records. Ask which route applies to the actual concern. Do not assume that one department can decide every kind of dispute.

Is an Acknowledgment the Same as a Resolution?

No. An acknowledgment confirms receipt at some level. A resolution needs a stated basis, such as an accepted explanation or a verified correction. Keep disputed answers and unanswered issues visible. If you close a file because you are pursuing another route, record that reason rather than calling the issue successfully resolved.

Does a Smaller Complaint Count Mean a Better DST Company?

Not without a reliable comparison. Counts depend on who is included, the period, and how an issue is defined. The route used and the handling of repeat messages also matter. Severity and outcome also matter. A small count with no total population cannot support a sound ranking. A larger firm may also use a different reporting system.

Should I Treat a Lower Distribution as Proof of Misconduct?

No. Match the period, interest, payment record, and stated calculation first. Identify the difference and request its explanation. A lower receipt can raise a serious question without establishing its cause. A target cash rate is also different from an approved payment and from the investment's total return.

Must Every Complaint Be Resolved Within Thirty Days?

This article found no basis for that blanket claim. The rule discussed above concerns certain member reports to FINRA. It does not set one reply deadline for all investors. Read the firm's actual wording and the legal rules that apply. Keep receipt, update, review, and final decision separate. Do not assign one clock to all four.

What Should I Keep When a Company Revises Its Answer?

Keep the earlier answer, the revised answer, the new source, and a short note explaining the change. Recheck any conclusions that depended on the old fact. Preserve the original dates. A revised answer can resolve a gap, create a new one, or leave the main issue disputed; the file should show which occurred.

Can a Regulator's Complaint Process Guarantee My Money Back?

No such guarantee is established here. A conduct review and a request for financial recovery can involve different processes and deadlines. Define the result you seek and obtain appropriate help with the available routes. Do not assume that waiting for an internal or regulatory response preserves every other option.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This article compares limited public routing instructions and explains how to assess evidence about investor concerns. It does not rate complaint outcomes, decide allegations, or provide a personal legal opinion.

Sources