Skip to content

testing long text #1050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
techeng322 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

testing long text #1050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/api/sms/toll-free/route.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ export async function GET(req: NextRequest) {
const phone_number = params.get("phone_number");
const messageParams = {
to: `+1${phone_number}` as string,
text: "In Process is testing phone number features. no action required.",
text: "Long Text Test: 'Someone is trying to connect this phone number to the artist profile for ... on In Process. If this was you, please reply 'yes'. If this was not you, please ignore this message.' no action required.",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Jan 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, locate and examine the file
find . -name "route.ts" -type f | grep -E "(sms|toll-free)" | head -20

Repository: sweetmantech/in_process

Length of output: 150

🏁 Script executed:

# Also search more broadly for SMS-related files
fd "route.ts" | grep -i sms

Repository: sweetmantech/in_process

Length of output: 144

🏁 Script executed:

# If that doesn't work, check the app directory structure
git ls-files | grep -E "app/api/sms" | head -20

Repository: sweetmantech/in_process

Length of output: 144

🏁 Script executed:

# Read the toll-free SMS route file to see the context
cat -n app/api/sms/toll-free/route.ts

Repository: sweetmantech/in_process

Length of output: 1915

🏁 Script executed:

# Also check the other SMS files for context on how they handle messages
cat -n app/api/sms/send/route.ts

Repository: sweetmantech/in_process

Length of output: 1667

🏁 Script executed:

# Count the exact character length of the SMS text
python3 << 'EOF'
text = "Long Text Test: 'Someone is trying to connect this phone number to the artist profile for ... on In Process. If this was you, please reply 'yes'. If this was not you, please ignore this message.' no action required."
print(f"Character count: {len(text)}")
print(f"GSM-7 segments (160 chars): {(len(text) + 159) // 160}")
print(f"Unicode segments (70 chars): {(len(text) + 69) // 70}")
print(f"\nText preview:")
print(text)
EOF

Repository: sweetmantech/in_process

Length of output: 153

🌐 Web query:

Telnyx SMS segmentation policy character limit multi-part messaging

💡 Result:

Short answer — Telnyx segmentation/limits (summary):

  • Encoding and per-segment sizes: GSM‑7 = 160 chars (single) / 153 chars (multi); UTF‑16 = 70 / 67; ASCII 8‑bit = 140 / 134. Telnyx uses these segmentation rules and falls back to UTF‑16 for non-GSM characters (emojis count against UTF‑16). (telnyx.mintlify.app) [1][2]

  • Maximum multipart segments: Telnyx bills and supports up to 10 segments per message; messages longer than that can be rejected. (support.telnyx.com) [3][4]

  • Billing: you are charged per message part/segment. Use Telnyx’s segment calculator to preview segments. (telnyx.mintlify.app) [1][5]

Sources:
[1] Telnyx Message Encoding / Segment Calculator (developer docs).
[2] Telnyx Toll‑Free Messaging — character/segmentation notes.
[3] Telnyx 10DLC FAQ — “We support up to 10 segments before messages will be rejected.”
[4] Telnyx resource: Mastering SMS character limits (FAQ about concatenation).
[5] Telnyx Messaging Pricing — charged per message part.

Citations:

🌐 Web query:

Telnyx SMS quote handling nested quotes encoding

💡 Result:

Short answer: escape quotes in your JSON payload (" for double quotes; or wrap the -d body in single quotes for curl) and be aware Telnyx will pick message encoding (GSM-7 vs UTF‑16) based on characters — extra/unusual quote characters can force UTF‑16 and increase parts/cost. See Telnyx send-message docs and their MDR/encoding note. [1][2]

Practical examples

  • JSON (safe for any client):
    {"from":"+1555…","to":"+1666…","text":"She said "Hello, world" and left."}
    (Double quotes inside the text must be escaped as ".)

  • curl (single-quoted -d avoids escaping double quotes):
    curl -X POST https://api.telnyx.com/v2/messages -H "Authorization: Bearer KEY" -H "Content-Type: application/json" -d '{"from":"+1…","to":"+1…","text":"She said "Hello""}'

Notes

  • If you include non‑GSM characters (e.g., smart/curly quotes “ ”) the message will use UTF‑16, reducing per‑part length and possibly increasing parts/cost. Check the message coding and parts in the MDR/logs. [2]
  • For webhooks/MDRs the body is stored/represented as JSON; check Telnyx docs if you need to parse stored message text. [1][2]

Sources

  • Telnyx Messaging API — send a message. [1]
  • Telnyx Help Center — SMS MDR / message coding and encoding details. [2]

🏁 Script executed:

# Let me manually count the character length of the SMS text
python3 << 'EOF'
text = "Long Text Test: 'Someone is trying to connect this phone number to the artist profile for ... on In Process. If this was you, please reply 'yes'. If this was not you, please ignore this message.' no action required."
char_count = len(text)
print(f"Character count: {char_count}")
print(f"GSM-7 single segment limit: 160 characters")
print(f"GSM-7 multi-segment per part: 153 characters")
print(f"Number of SMS segments needed (GSM-7): {(char_count + 152) // 153}")
print(f"Will trigger multi-part SMS: {char_count > 160}")
EOF

Repository: sweetmantech/in_process

Length of output: 250

Simplify SMS text to fit single segment and remove nested quote redundancy.

The SMS text is 215 characters—exceeding Telnyx's 160-character GSM-7 limit—and will be sent as 2 segments (costing 2x). Remove the outer quotes or rephrase to reduce length and clarity. For example, replace 'Someone is trying to connect... please reply 'yes'...' with Someone is trying to connect... please reply yes... to fit within 160 characters and eliminate the confusing nested quotes.

🤖 Prompt for AI Agents 
In @app/api/sms/toll-free/route.ts at line 21, The SMS message assigned to the
text property in the toll-free route (the object with key "text" in
app/api/sms/toll-free/route.ts) is 215 characters and contains nested quotes;
shorten and simplify it to <=160 GSM-7 chars and remove inner single
quotes—e.g., rephrase to "Someone is trying to connect this phone number to the
artist profile for ... on In Process. If this was you please reply yes. If not,
ignore."—so the single-segment SMS fits Telnyx limits and avoids redundant
quotes.

type: "SMS" as const,
messaging_profile_id: TELNYX_MESSAGING_PROFILE_ID,
};
Expand Down