# SendSms - Advanced Documentation

## Model Shape (CorrespondenceInfo)

ShortMessage is required.
From is required, but the server always overwrites it with the authenticated user regardless of what is sent.

## When to Use

**Send an SMS that is not tied to any claim or contact.** Designed for headless/script use cases - e.g., an AI chatbot sending a text notification to staff. The correspondence is not persisted to the database; it is fire-and-forget.

If you need to send an SMS associated with a claim or contact (and have it saved as a correspondence record), use `SendCorrespondenceSms` instead.

## Key Behavior

- **No claims or contacts allowed.** If `Claims` or `Contacts` arrays are populated, the endpoint throws `RadoloException`.
- **No persistence.** The correspondence is sent but not saved to the database. There will be no correspondence record to reference later.
- **Action is always Create.** The endpoint hardcodes the action - callers do not specify it.
- **ProcessID required.** Used for background process status tracking (`Controllers.ProcessStatus`).

## Script Example

```javascript
async () => {
  const correspondence = {
    ShortMessage: "You have been assigned to a new case. Please review in Backdocket.",
    From: {
      Value: "+15551234567",
      Name: "Firm Notifications"
    },
    Tos: [
      {
        Value: "+15559876543",
        Name: "John Smith"
      }
    ]
  };

  const result = await SecureApi.SendSms("process-1", correspondence);
  return {
    status: result.Status,
    shortMessage: result.ShortMessage
  };
}
```

## Cross-References

| Need | Use Instead |
|------|-------------|
| SMS tied to a claim/contact (persisted) | `SendCorrespondenceSms(ProcessID, Action, Correspondence)` |
| Email without claim/contact | `SendEmail(ProcessID, Correspondence)` |
| Email tied to a claim/contact (persisted) | `SendCorrespondenceEmail(ProcessID, Action, Correspondence)` |